INFO: trying to register non-static key.
the code is fine but needs lockdep annotation.
turning off the locking correctness validator.
CPU: 1 PID: 11943 Comm: syz-executor.0 Not tainted 4.14.307-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
 __dump_stack lib/dump_stack.c:17 [inline]
 dump_stack+0x1b2/0x281 lib/dump_stack.c:58
 register_lock_class+0x389/0x1180 kernel/locking/lockdep.c:768
 __lock_acquire+0x167/0x3f20 kernel/locking/lockdep.c:3378
 lock_acquire+0x170/0x3f0 kernel/locking/lockdep.c:3998
 flush_work+0xad/0x770 kernel/workqueue.c:2890
 __cancel_work_timer+0x321/0x460 kernel/workqueue.c:2965
 smc_close_active+0x7e2/0xbb0 net/smc/smc_close.c:207
 smc_release+0x3e1/0x5d0 net/smc/af_smc.c:131
 __sock_release+0xcd/0x2b0 net/socket.c:602
 sock_close+0x15/0x20 net/socket.c:1139
 __fput+0x25f/0x7a0 fs/file_table.c:210
 task_work_run+0x11f/0x190 kernel/task_work.c:113
 tracehook_notify_resume include/linux/tracehook.h:191 [inline]
 exit_to_usermode_loop+0x1ad/0x200 arch/x86/entry/common.c:164
 prepare_exit_to_usermode arch/x86/entry/common.c:199 [inline]
 syscall_return_slowpath arch/x86/entry/common.c:270 [inline]
 do_syscall_64+0x4a3/0x640 arch/x86/entry/common.c:297
 entry_SYSCALL_64_after_hwframe+0x5e/0xd3
RIP: 0033:0x7f433d23ffab
RSP: 002b:00007ffffdff90d0 EFLAGS: 00000293 ORIG_RAX: 0000000000000003
RAX: 0000000000000000 RBX: 0000000000000005 RCX: 00007f433d23ffab
RDX: 00007f433ce02c28 RSI: ffffffffffffffff RDI: 0000000000000004
RBP: 00007f433d3af980 R08: 0000000000000000 R09: 00007f433ce02000
R10: 00007f433ce02c30 R11: 0000000000000293 R12: 0000000000048b9f
R13: 00007ffffdff91d0 R14: 00007f433d3adf80 R15: 0000000000000032
audit: type=1804 audit(1678149405.824:3): pid=11973 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1817934910/syzkaller.VdoAnv/153/bus" dev="sda1" ino=14213 res=1
L1TF CPU bug present and SMT on, data leak possible. See CVE-2018-3646 and https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/l1tf.html for details.
XFS (loop2): correcting sb_features alignment problem
syz-executor.3 (11947) used greatest stack depth: 24928 bytes left
XFS (loop2): Mounting V4 Filesystem
XFS (loop2): totally zeroed log
XFS (loop2): failed to read root inode
audit: type=1804 audit(1678149406.724:4): pid=12054 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.5" name="/root/syzkaller-testdir1817934910/syzkaller.VdoAnv/154/bus" dev="sda1" ino=14233 res=1
audit: type=1804 audit(1678149406.754:5): pid=12073 uid=0 auid=4294967295 ses=4294967295 op="invalid_pcr" cause="open_writers" comm="syz-executor.0" name="/root/syzkaller-testdir1571827822/syzkaller.oOORxn/163/bus" dev="sda1" ino=14234 res=1
XFS (loop2): correcting sb_features alignment problem
XFS (loop2): Mounting V4 Filesystem
XFS (loop2): totally zeroed log
XFS (loop2): failed to read root inode
XFS (loop2): correcting sb_features alignment problem
XFS (loop2): Mounting V4 Filesystem
XFS (loop2): totally zeroed log
XFS (loop2): failed to read root inode
capability: warning: `syz-executor.2' uses 32-bit capabilities (legacy support in use)