diff options
author | Nathan Chancellor <nathan@kernel.org> | 2025-05-13 00:16:55 +0200 |
---|---|---|
committer | Thomas Gleixner <tglx@linutronix.de> | 2025-05-13 09:37:18 +0200 |
commit | b5fcb6898202858ae8425bf0cd9cb5704735bd02 (patch) | |
tree | 03b76585e0b509d78eaaad16b2f904c45587bab7 /scripts/gdb/linux/utils.py | |
parent | c1ab449df871d6ce9189cb0a9efcd37d2ead10f0 (diff) |
genirq: Ensure flags in lock guard is consistently initialized
After the conversion to locking guards within the interrupt core code,
several builds with clang show the "Interrupts were enabled early"
WARN() in start_kernel() on boot.
In class_irqdesc_lock_constructor(), _t.flags is initialized via
__irq_get_desc_lock() within the _t initializer list. However, the C11
standard 6.7.9.23 states that the evaluation of the initialization list
expressions are indeterminately sequenced relative to one another,
meaning _t.flags could be initialized by __irq_get_desc_lock() then be
initialized to zero due to flags being absent from the initializer list.
To ensure _t.flags is consistently initialized, move the call to
__irq_get_desc_lock() and the assignment of its result to _t.lock out of
the designated initializer.
Fixes: 0f70a49f3fa3 ("genirq: Provide conditional lock guards")
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
Reviewed-by: Jiri Slaby <jirislaby@kernel.org>
Link: https://lore.kernel.org/all/20250513-irq-guards-fix-flags-init-v1-1-1dca3f5992d6@kernel.org
Diffstat (limited to 'scripts/gdb/linux/utils.py')
0 files changed, 0 insertions, 0 deletions