Fix the KCSAN_ENABLED check when building modules
The KCSAN_ENABLED variable is non-empty when the kernel is being built with KCSAN. This allows us to disable modules that are known to be broken. There was a bug where we would check if it was defined. As this is always the case the KCSAN_ENABLED variable would be set when building modules so we would never build such a module. Fix this by checking if the value is empty before passing it on to the module stage. This doesn't affect how modules are built as the CFLAGS passed to modules has the correct check. Reported by: rstone Sponsored by: Innovate UK
This commit is contained in:
parent
0a0d6ce34d
commit
2422138952
@ -38,7 +38,7 @@ MKMODULESENV+= WITH_CTF="${WITH_CTF}"
|
||||
MKMODULESENV+= WITH_EXTRA_TCP_STACKS="${WITH_EXTRA_TCP_STACKS}"
|
||||
.endif
|
||||
|
||||
.if defined(KCSAN_ENABLED)
|
||||
.if !empty(KCSAN_ENABLED)
|
||||
MKMODULESENV+= KCSAN_ENABLED="yes"
|
||||
.endif
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user