syzbot wrote: > Hello, > > syzbot found the following issue on: > > HEAD commit: 9c54130c Add linux-next specific files for 20210406 > git tree: linux-next > console output: https://syzkaller.appspot.com/x/log.txt?x=17d8d7aad00000 > kernel config: https://syzkaller.appspot.com/x/.config?x=d125958c3995ddcd > dashboard link: https://syzkaller.appspot.com/bug?extid=b54a1ce86ba4a623b7f0 > syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1729797ed00000 > C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1190f46ad00000 > > The issue was bisected to: > > commit 997acaf6b4b59c6a9c259740312a69ea549cc684 > Author: Mark Rutland <mark.rutland@xxxxxxx> > Date: Mon Jan 11 15:37:07 2021 +0000 > > lockdep: report broken irq restoration > > bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=11a6cc96d00000 > final oops: https://syzkaller.appspot.com/x/report.txt?x=13a6cc96d00000 > console output: https://syzkaller.appspot.com/x/log.txt?x=15a6cc96d00000 > > IMPORTANT: if you fix the issue, please add the following tag to the commit: > Reported-by: syzbot+b54a1ce86ba4a623b7f0@xxxxxxxxxxxxxxxxxxxxxxxxx > Fixes: 997acaf6b4b5 ("lockdep: report broken irq restoration") > > ------------[ cut here ]------------ > refcount_t: saturated; leaking memory. > WARNING: CPU: 1 PID: 8414 at lib/refcount.c:19 refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19 > Modules linked in: > CPU: 1 PID: 8414 Comm: syz-executor793 Not tainted 5.12.0-rc6-next-20210406-syzkaller #0 > Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 > RIP: 0010:refcount_warn_saturate+0xf4/0x1e0 lib/refcount.c:19 > Code: 1d 69 0c e6 09 31 ff 89 de e8 c8 b4 a6 fd 84 db 75 ab e8 0f ae a6 fd 48 c7 c7 e0 52 c2 89 c6 05 49 0c e6 09 01 e8 91 0f 00 05 <0f> 0b eb 8f e8 f3 ad a6 fd 0f b6 1d 33 0c e6 09 31 ff 89 de e8 93 > RSP: 0018:ffffc90000eef388 EFLAGS: 00010282 > RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000000000000 > RDX: ffff88801bbdd580 RSI: ffffffff815c2e05 RDI: fffff520001dde63 > RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000 > R10: ffffffff815bcc6e R11: 0000000000000000 R12: 1ffff920001dde74 > R13: 0000000090200301 R14: ffff888026e00000 R15: ffffc90000eef3c0 > FS: 0000000001422300(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000 > CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 > CR2: 0000000020000000 CR3: 0000000012b3b000 CR4: 00000000001506e0 > DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 > DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 > Call Trace: > __refcount_add_not_zero include/linux/refcount.h:163 [inline] > __refcount_inc_not_zero include/linux/refcount.h:227 [inline] > refcount_inc_not_zero include/linux/refcount.h:245 [inline] > sk_psock_get+0x3b0/0x400 include/linux/skmsg.h:435 > bpf_exec_tx_verdict+0x11e/0x11a0 net/tls/tls_sw.c:799 > tls_sw_sendmsg+0xa41/0x1800 net/tls/tls_sw.c:1013 > inet_sendmsg+0x99/0xe0 net/ipv4/af_inet.c:821 [...] This is likely a problem with latest round of sockmap patches I'll tke a look.
