Hello, syzbot found the following crash on: HEAD commit: 5a9ffb95 Merge tag '5.7-rc5-smb3-fixes' of git://git.samba.. git tree: upstream console output: https://syzkaller.appspot.com/x/log.txt?x=175e90d6100000 kernel config: https://syzkaller.appspot.com/x/.config?x=c14212794ed9ad24 dashboard link: https://syzkaller.appspot.com/bug?extid=78cf4962d1cf5f23a0c9 compiler: gcc (GCC) 9.0.0 20181231 (experimental) Unfortunately, I don't have any reproducer for this crash yet. IMPORTANT: if you fix the bug, please add the following tag to the commit: Reported-by: syzbot+78cf4962d1cf5f23a0c9@xxxxxxxxxxxxxxxxxxxxxxxxx INFO: trying to register non-static key. the code is fine but needs lockdep annotation. turning off the locking correctness validator. CPU: 1 PID: 235 Comm: kworker/u4:5 Not tainted 5.7.0-rc5-syzkaller #0 Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011 Workqueue: krdsd rds_tcp_accept_worker Call Trace: __dump_stack lib/dump_stack.c:77 [inline] dump_stack+0x188/0x20d lib/dump_stack.c:118 assign_lock_key kernel/locking/lockdep.c:913 [inline] register_lock_class+0x1664/0x1760 kernel/locking/lockdep.c:1225 __lock_acquire+0x104/0x4c50 kernel/locking/lockdep.c:4234 lock_acquire+0x1f2/0x8f0 kernel/locking/lockdep.c:4934 __raw_spin_lock_irq include/linux/spinlock_api_smp.h:128 [inline] _raw_spin_lock_irq+0x5b/0x80 kernel/locking/spinlock.c:167 spin_lock_irq include/linux/spinlock.h:378 [inline] clear_inode+0x1b/0x1e0 fs/inode.c:529 evict+0x4ee/0x650 fs/inode.c:579 iput_final fs/inode.c:1572 [inline] iput+0x536/0x8c0 fs/inode.c:1598 __sock_release+0x20c/0x280 net/socket.c:617 rds_tcp_accept_one+0x582/0xb70 net/rds/tcp_listen.c:251 rds_tcp_accept_worker+0x50/0x80 net/rds/tcp.c:525 process_one_work+0x965/0x16a0 kernel/workqueue.c:2268 worker_thread+0x96/0xe20 kernel/workqueue.c:2414 kthread+0x388/0x470 kernel/kthread.c:268 ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:351 --- This bug 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 bug report. See: https://goo.gl/tpsmEJ#status for how to communicate with syzbot.
