aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/syscall-counts.py
diff options
context:
space:
mode:
authorGuilherme G. Piccoli <[email protected]>2022-09-09 17:07:55 -0300
committerGreg Kroah-Hartman <[email protected]>2022-09-24 14:59:44 +0200
commit3e081438b8e639cc76ef1a5ce0c1bd8a154082c7 (patch)
tree5ea113fbc98d460da5135f911d9c3a9ad8750ab2 /tools/perf/scripts/python/syscall-counts.py
parenta5ccec12acfaf3a7ebbbeb90555b35b275fce0df (diff)
firmware: google: Test spinlock on panic path to avoid lockups
Currently the gsmi driver registers a panic notifier as well as reboot and die notifiers. The callbacks registered are called in atomic and very limited context - for instance, panic disables preemption and local IRQs, also all secondary CPUs (not executing the panic path) are shutdown. With that said, taking a spinlock in this scenario is a dangerous invitation for lockup scenarios. So, fix that by checking if the spinlock is free to acquire in the panic notifier callback - if not, bail-out and avoid a potential hang. Fixes: 74c5b31c6618 ("driver: Google EFI SMI") Cc: Andrew Morton <[email protected]> Cc: Ard Biesheuvel <[email protected]> Cc: David Gow <[email protected]> Cc: Greg Kroah-Hartman <[email protected]> Cc: Julius Werner <[email protected]> Cc: Petr Mladek <[email protected]> Reviewed-by: Evan Green <[email protected]> Signed-off-by: Guilherme G. Piccoli <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions