mirror of
https://github.com/torvalds/linux.git
synced 2025-12-07 20:06:24 +00:00
seqlock: Allow KASAN to fail optimizing
Some KASAN builds are failing to properly optimize this code -- luckily we don't care about core quality for KASAN builds, so just exclude it. Reported-by: kernel test robot <lkp@intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Closes: https://lore.kernel.org/oe-kbuild-all/202510251641.idrNXhv5-lkp@intel.com/
This commit is contained in:
@@ -1234,11 +1234,14 @@ static inline void __scoped_seqlock_cleanup(struct ss_tmp *sst)
|
||||
|
||||
extern void __scoped_seqlock_invalid_target(void);
|
||||
|
||||
#if defined(CONFIG_CC_IS_GCC) && CONFIG_GCC_VERSION < 90000
|
||||
#if (defined(CONFIG_CC_IS_GCC) && CONFIG_GCC_VERSION < 90000) || defined(CONFIG_KASAN)
|
||||
/*
|
||||
* For some reason some GCC-8 architectures (nios2, alpha) have trouble
|
||||
* determining that the ss_done state is impossible in __scoped_seqlock_next()
|
||||
* below.
|
||||
*
|
||||
* Similarly KASAN is known to confuse compilers enough to break this. But we
|
||||
* don't care about code quality for KASAN builds anyway.
|
||||
*/
|
||||
static inline void __scoped_seqlock_bug(void) { }
|
||||
#else
|
||||
|
||||
Reference in New Issue
Block a user