Hello,
syzbot found the following issue on:
HEAD commit: 3f8a27f9e27b Linux 4.19.211
git tree: linux-4.19.y
console output:
https://syzkaller.appspot.com/x/log.txt?x=16eb9fd2c80000
kernel config:
https://syzkaller.appspot.com/x/.config?x=9b9277b418617afe
dashboard link:
https://syzkaller.appspot.com/bug?extid=f6b72483b11601cf9c87
compiler: gcc version 10.2.1 20210110 (Debian 10.2.1-6)
Unfortunately, I don't have any reproducer for this issue yet.
Downloadable assets:
disk image:
https://storage.googleapis.com/syzbot-assets/98c0bdb4abb3/disk-3f8a27f9.raw.xz
vmlinux:
https://storage.googleapis.com/syzbot-assets/ea228ff02669/vmlinux-3f8a27f9.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by:
syzbot+f6b724...@syzkaller.appspotmail.com
WARNING: CPU: 1 PID: 10585 at kernel/locking/lockdep.c:698 arch_local_save_flags arch/x86/include/asm/paravirt.h:784 [inline]
WARNING: CPU: 1 PID: 10585 at kernel/locking/lockdep.c:698 look_up_lock_class kernel/locking/lockdep.c:689 [inline]
WARNING: CPU: 1 PID: 10585 at kernel/locking/lockdep.c:698 register_lock_class+0x77b/0x11c0 kernel/locking/lockdep.c:749
Kernel panic - not syncing: panic_on_warn set ...
CPU: 1 PID: 10585 Comm: syz-executor.5 Not tainted 4.19.211-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 03/02/2023
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2ef lib/dump_stack.c:118
panic+0x26a/0x50e kernel/panic.c:186
__warn.cold+0x20/0x5a kernel/panic.c:541
report_bug+0x262/0x2b0 lib/bug.c:183
fixup_bug arch/x86/kernel/traps.c:178 [inline]
fixup_bug arch/x86/kernel/traps.c:173 [inline]
do_error_trap+0x1d7/0x310 arch/x86/kernel/traps.c:296
BTRFS: device fsid 24c7a497-3402-47dd-bef8-82358f5f30e0 devid 1 transid 8 /dev/loop4
invalid_op+0x14/0x20 arch/x86/entry/entry_64.S:1038
RIP: 0010:look_up_lock_class kernel/locking/lockdep.c:698 [inline]
RIP: 0010:register_lock_class+0x77b/0x11c0 kernel/locking/lockdep.c:749
Code: 8b 05 c9 63 ec 0b 85 c0 0f 85 17 ff ff ff 48 c7 c6 e0 1b 6a 88 48 c7 c7 40 19 6a 88 e8 c3 29 a8 06 0f 0b e9 fd fe ff ff 0f 0b <0f> 0b e9 b3 fa ff ff 48 8d 70 01 48 69 c0 50 01 00 00 48 89 35 ac
RSP: 0018:ffff888045c1fac8 EFLAGS: 00010087
RAX: dffffc0000000000 RBX: ffff8880a49850e0 RCX: 0000000000000000
RDX: 1ffff11014930a1f RSI: 0000000000000000 RDI: ffff8880a49850f8
RBP: 0000000000000000 R08: 0000000000000000 R09: 1ffff11008b83f61
R10: ffffffff8d243760 R11: 0000000000000000 R12: ffffffff8cdd3fe0
R13: ffffffff894c35a0 R14: 1ffff11008b83f61 R15: 0000000000000000
__lock_acquire+0x17d/0x3ff0 kernel/locking/lockdep.c:3304
attempt to access beyond end of device
lock_acquire+0x170/0x3c0 kernel/locking/lockdep.c:3908
__raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline]
_raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:168
spin_lock_bh include/linux/spinlock.h:334 [inline]
lock_sock_nested+0x3b/0x110 net/core/sock.c:2884
lock_sock include/net/sock.h:1512 [inline]
inet_shutdown+0x7d/0x3a0 net/ipv4/af_inet.c:852
__sys_shutdown+0xf3/0x1a0 net/socket.c:2077
loop2: rw=1, want=77832, limit=63271
__do_sys_shutdown net/socket.c:2085 [inline]
__se_sys_shutdown net/socket.c:2083 [inline]
__x64_sys_shutdown+0x50/0x70 net/socket.c:2083
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x7fadd1bee0f9
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fadd013f168 EFLAGS: 00000246 ORIG_RAX: 0000000000000030
RAX: ffffffffffffffda RBX: 00007fadd1d0e050 RCX: 00007fadd1bee0f9
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000006
RBP: 00007fadd1c49ae9 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffc9e5d09f R14: 00007fadd013f300 R15: 0000000000022000
Kernel Offset: disabled
Rebooting in 86400 seconds..
---
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
syzk...@googlegroups.com.
syzbot will keep track of this issue. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.