-
None of these functions are called over interrupt context. Leaving the critical sections interruptible can cause premature/double-unlock scenarios and bug reports such as [Xenomai] lock ffffffff81c56000 already unlocked on CPU #1 last owner = kernel/xenomai/debug.c:74 (hash_symbol(), CPU #1) 000000000000002f ffff88007dc8bb10 ffffffff8118ae8f ffffffff00000001 0000000000000021 ffff88007f897fde ffff88007dc8bb50 ffffffff8118b266 00000000000000f1 ffff88007dc8bd68 0000000000000006 ffff88007dc8bd40 Call Trace: [<ffffffff8118ae8f>] xnlock_dbg_release+0xdf/0xf0 [<ffffffff8118b266>] hash_symbol+0x236/0x2d0 [<ffffffff8118b668>] xndebug_trace_relax+0x118/0x450 [<ffffffff811b8d50>] ? CoBaLt32emu_mmap+0xf0/0xf0 [<ffffffff811b8dd7>] CoBaLt32emu_backtrace+0x87/0xb0 [<ffffffff8100def6>] ? fpu__clear+0xd6/0x160 [<ffffffff817b3691>] ? _raw_spin_unlock_irq+0x11/0x30 [<ffffffff811ab1cc>] ipipe_syscall_hook+0x11c/0x3a0 [<ffffffff8113d9bf>] __ipipe_notify_syscall+0xbf/0x180 [<ffffffff810cd019>] ? __set_current_blocked+0x49/0x50 [<ffffffff8113daab>] ipipe_handle_syscall+0x2b/0xb0 [<ffffffff81001c9d>] do_fast_syscall_32+0xbd/0x220 [<ffffffff817b64e2>] sysenter_flags_fixed+0x8/0x12 Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
5036abbe