Hello, syzbot found the following issue on: HEAD commit: 6f923748057a Add linux-next specific files for 20240827 git tree: linux-next console output: https://syzkaller.appspot.com/x/log.txt?x=105f7791980000 kernel config: https://syzkaller.appspot.com/x/.config?x=65c4a779aad2633f dashboard link: https://syzkaller.appspot.com/bug?extid=b467973d2dd3b9deaa1f 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/4398d0ec73ed/disk-6f923748.raw.xz vmlinux: https://storage.googleapis.com/syzbot-assets/1f7e004ef90a/vmlinux-6f923748.xz kernel image: https://storage.googleapis.com/syzbot-assets/333e975a3aac/bzImage-6f923748.xz IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+b467973d2dd3b9deaa1f@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(chain_key != INITIAL_CHAIN_KEY) WARNING: CPU: 0 PID: 5320 at kernel/locking/lockdep.c:5180 __lock_acquire+0x1659/0x2050 kernel/locking/lockdep.c:5180 Modules linked in: CPU: 0 UID: 0 PID: 5320 Comm: syz.2.7 Not tainted 6.11.0-rc5-next-20240827-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 08/06/2024 RIP: 0010:__lock_acquire+0x1659/0x2050 kernel/locking/lockdep.c:5180 Code: 0f b6 04 08 84 c0 0f 85 e9 09 00 00 83 3d 0e 40 ac 0e 00 75 19 90 48 c7 c7 60 c9 0a 8c 48 c7 c6 a0 f2 0a 8c e8 88 7c e5 ff 90 <0f> 0b 90 90 90 45 31 f6 e9 aa fd ff ff 48 89 d3 e8 32 99 42 03 e8 RSP: 0018:ffffc900043d6ff0 EFLAGS: 00010046 RAX: 21b44eb71ffad700 RBX: ffff888020550ad0 RCX: ffff888020550000 RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000 RBP: ffff888020550ae0 R08: ffffffff8155a5b2 R09: fffffbfff1cfa364 R10: dffffc0000000000 R11: fffffbfff1cfa364 R12: 0000000000000001 R13: ffff888020550ad8 R14: 58cce5e7c8d5ebdc R15: ffff888020550b00 FS: 0000000000000000(0000) GS:ffff8880b9000000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00000000200000f0 CR3: 00000000662b2000 CR4: 00000000003526f0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> lock_acquire+0x1ed/0x550 kernel/locking/lockdep.c:5825 rcu_lock_acquire include/linux/rcupdate.h:337 [inline] rcu_read_lock include/linux/rcupdate.h:849 [inline] search_bpf_extables+0x42/0x3f0 kernel/bpf/core.c:788 fixup_exception+0xaf/0x1cc0 arch/x86/mm/extable.c:320 </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
