Hello, syzbot found the following issue on: HEAD commit: f11ee2ad25b2 net: mana: Prefer struct_size over open coded.. git tree: net console output: https://syzkaller.appspot.com/x/log.txt?x=14a96963300000 kernel config: https://syzkaller.appspot.com/x/.config?x=16e23f04679ec35e dashboard link: https://syzkaller.appspot.com/bug?extid=91ba852bd0ad0581a0e3 compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.1 Unfortunately, I don't have any reproducer for this issue yet. IMPORTANT: if you fix the issue, please add the following tag to the commit: Reported-by: syzbot+91ba852bd0ad0581a0e3@xxxxxxxxxxxxxxxxxxxxxxxxx ------------[ cut here ]------------ DEBUG_LOCKS_WARN_ON(1) WARNING: CPU: 1 PID: 32344 at kernel/locking/lockdep.c:203 hlock_class kernel/locking/lockdep.c:203 [inline] WARNING: CPU: 1 PID: 32344 at kernel/locking/lockdep.c:203 hlock_class kernel/locking/lockdep.c:192 [inline] WARNING: CPU: 1 PID: 32344 at kernel/locking/lockdep.c:203 check_wait_context kernel/locking/lockdep.c:4688 [inline] WARNING: CPU: 1 PID: 32344 at kernel/locking/lockdep.c:203 __lock_acquire+0x1344/0x54a0 kernel/locking/lockdep.c:4965 Modules linked in: CPU: 1 PID: 32344 Comm: kworker/1:0 Not tainted 5.14.0-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: events sco_sock_timeout RIP: 0010:hlock_class kernel/locking/lockdep.c:203 [inline] RIP: 0010:hlock_class kernel/locking/lockdep.c:192 [inline] RIP: 0010:check_wait_context kernel/locking/lockdep.c:4688 [inline] RIP: 0010:__lock_acquire+0x1344/0x54a0 kernel/locking/lockdep.c:4965 Code: 08 84 d2 0f 85 f1 3d 00 00 8b 05 df 9a 13 0c 85 c0 0f 85 f4 fd ff ff 48 c7 c6 60 03 8c 89 48 c7 c7 20 f7 8b 89 e8 79 ff 96 07 <0f> 0b 31 ed e9 b7 f0 ff ff e8 de 49 7b 02 85 c0 0f 84 12 fe ff ff RSP: 0018:ffffc900161efa88 EFLAGS: 00010082 RAX: 0000000000000000 RBX: ffff88801ec820a0 RCX: 0000000000000000 RDX: ffff8880247b9c80 RSI: ffffffff815dbd58 RDI: fffff52002c3df43 RBP: 0000000000000b04 R08: 0000000000000000 R09: 0000000000000000 R10: ffffffff815d5afe R11: 0000000000000000 R12: ffff8880247ba6c8 R13: ffff8880247b9c80 R14: 0000000000040000 R15: 0000000000040b04 FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 00007fc98ea0b718 CR3: 000000001cc2b000 CR4: 00000000001506e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: lock_acquire kernel/locking/lockdep.c:5625 [inline] lock_acquire+0x1ab/0x510 kernel/locking/lockdep.c:5590 __raw_spin_lock_bh include/linux/spinlock_api_smp.h:135 [inline] _raw_spin_lock_bh+0x2f/0x40 kernel/locking/spinlock.c:178 spin_lock_bh include/linux/spinlock.h:368 [inline] lock_sock_nested+0x40/0x120 net/core/sock.c:3183 lock_sock include/net/sock.h:1612 [inline] sco_sock_timeout+0xd2/0x290 net/bluetooth/sco.c:96 process_one_work+0x9bf/0x16b0 kernel/workqueue.c:2297 worker_thread+0x658/0x11f0 kernel/workqueue.c:2444 kthread+0x3e5/0x4d0 kernel/kthread.c:319 ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:295 --- 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.
