Hello, syzbot found the following issue on: HEAD commit: 0fc810ae3ae1 x86/uaccess: Avoid barrier_nospec() in 64-bit.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=15ac9340580000 kernel config: https://syzkaller.appspot.com/x/.config?x=4aec7739e14231a7 dashboard link: https://syzkaller.appspot.com/bug?extid=a617d4c5ff27f35f8255 compiler: Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40 Unfortunately, I don't have any reproducer for this issue yet. Downloadable assets: disk image: https://storage.googleapis.com/syzbot-assets/d7ec34ee152e/disk-0fc810ae.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/ba87040ccb6c/vmlinux-0fc810ae.xz kernel image: https://storage.googleapis.com/syzbot-assets/0e189a9b5a22/bzImage-0fc810ae.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+a617d4c5ff27f35f8255@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ WARNING: CPU: 1 PID: 8645 at kernel/rcu/srcutree.c:656 cleanup_srcu_struct+0x404/0x4d0 kernel/rcu/srcutree.c:656 Modules linked in: CPU: 1 UID: 0 PID: 8645 Comm: kworker/u8:11 Not tainted 6.12.0-rc5-syzkaller-00063-g0fc810ae3ae1 #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 09/13/2024 Workqueue: ib-unreg-wq ib_unregister_work RIP: 0010:cleanup_srcu_struct+0x404/0x4d0 kernel/rcu/srcutree.c:656 Code: 4d 84 00 48 c7 03 00 00 00 00 48 83 c4 48 5b 41 5c 41 5d 41 5e 41 5f 5d e9 84 f4 75 0a 90 0f 0b 90 eb e7 90 0f 0b 90 eb e1 90 <0f> 0b 90 eb db 90 0f 0b 90 eb 0a 90 0f 0b 90 eb 04 90 0f 0b 90 48 RSP: 0018:ffffc90003f07930 EFLAGS: 00010202 RAX: 0000000000000001 RBX: ffff888079789980 RCX: 0000000000000002 RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffe8ffffd59658 RBP: 0000000000000001 R08: ffffe8ffffd5965f R09: 1ffffd1ffffab2cb R10: dffffc0000000000 R11: fffff91ffffab2cc R12: dffffc0000000000 R13: ffff88805bab05e8 R14: ffff88805bab0000 R15: ffff888079789800 FS: 0000000000000000(0000) GS:ffff8880b8700000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007f7b86306d58 CR3: 0000000060ea6000 CR4: 0000000000350ef0 Call Trace: <TASK> ib_uverbs_release_dev+0x4e/0x80 drivers/infiniband/core/uverbs_main.c:136 device_release+0x9b/0x1c0 kobject_cleanup lib/kobject.c:689 [inline] kobject_release lib/kobject.c:720 [inline] kref_put include/linux/kref.h:65 [inline] kobject_put+0x231/0x480 lib/kobject.c:737 remove_client_context+0xb9/0x1e0 drivers/infiniband/core/device.c:782 disable_device+0x13b/0x360 drivers/infiniband/core/device.c:1288 __ib_unregister_device+0x2ac/0x3d0 drivers/infiniband/core/device.c:1518 ib_unregister_work+0x19/0x30 drivers/infiniband/core/device.c:1630 process_one_work kernel/workqueue.c:3229 [inline] process_scheduled_works+0xa65/0x1850 kernel/workqueue.c:3310 worker_thread+0x870/0xd30 kernel/workqueue.c:3391 kthread+0x2f2/0x390 kernel/kthread.c:389 ret_from_fork+0x4d/0x80 arch/x86/kernel/process.c:147 ret_from_fork_asm+0x1a/0x30 arch/x86/entry/entry_64.S:244 </TASK> --- This report is generated by a bot. It may contain errors. See https://goo.gl/tpsmEJ for more information about syzbot. syzbot engineers can be reached at syzkaller@xxxxxxxxxxxxxxxx. syzbot will keep track of this issue. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot. If the report is already addressed, let syzbot know by replying with: #syz fix: exact-commit-title If you want to overwrite report's subsystems, reply with: #syz set subsystems: new-subsystem (See the list of subsystem names on the web dashboard) If the report is a duplicate of another one, reply with: #syz dup: exact-subject-of-another-report If you want to undo deduplication, reply with: #syz undup
