summaryrefslogtreecommitdiffstats
path: root/security
diff options
context:
space:
mode:
authorThomas Gleixner <tglx@linutronix.de>2021-02-10 00:40:43 +0100
committerThomas Gleixner <tglx@linutronix.de>2021-02-10 23:34:13 +0100
commite7f89001797148e8dc7060c335df2c56e73a8c7a (patch)
tree6fd44fa30593a4d513f47aa7c1c80d4f3ec588ab /security
parentx86/entry: Fix instrumentation annotation (diff)
downloadlinux-e7f89001797148e8dc7060c335df2c56e73a8c7a.tar.xz
linux-e7f89001797148e8dc7060c335df2c56e73a8c7a.zip
x86/irq: Sanitize irq stack tracking
The recursion protection for hard interrupt stacks is an unsigned int per CPU variable initialized to -1 named __irq_count. The irq stack switching is only done when the variable is -1, which creates worse code than just checking for 0. When the stack switching happens it uses this_cpu_add/sub(1), but there is no reason to do so. It simply can use straight writes. This is a historical leftover from the low level ASM code which used inc and jz to make a decision. Rename it to hardirq_stack_inuse, make it a bool and use plain stores. Signed-off-by: Thomas Gleixner <tglx@linutronix.de> Reviewed-by: Kees Cook <keescook@chromium.org> Link: https://lore.kernel.org/r/20210210002512.228830141@linutronix.de
Diffstat (limited to 'security')
0 files changed, 0 insertions, 0 deletions