general protection fault in sock_release

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1c273e10 Merge tag 'zonefs-5.12-rc4' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=12aa6301d00000
kernel config: https://syzkaller.appspot.com/x/.config?x=c51293a9ca630f6d
dashboard link: https://syzkaller.appspot.com/bug?extid=84b87d0226dab4b69d95
compiler: Debian clang version 11.0.1-2
CC: [and...@kernel.org a...@kernel.org b...@vger.kernel.org dan...@iogearbox.net da...@davemloft.net john.fa...@gmail.com ka...@fb.com kps...@kernel.org ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org songliu...@fb.com y...@fb.com]

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+84b87d...@syzkaller.appspotmail.com

general protection fault, probably for non-canonical address 0xfff10c0e7dfbf004: 0000 [#1] PREEMPT SMP KASAN
KASAN: maybe wild-memory-access in range [0xff888073efdf8020-0xff888073efdf8027]
CPU: 0 PID: 11296 Comm: kworker/u4:8 Not tainted 5.12.0-rc3-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Workqueue: netns cleanup_net
RIP: 0010:__sock_release net/socket.c:594 [inline]
RIP: 0010:sock_release+0x24/0x140 net/socket.c:627
Code: f9 eb 8a 0f 1f 00 41 57 41 56 41 54 53 49 89 fe 49 bc 00 00 00 00 00 fc ff df e8 67 53 f4 f9 49 8d 5e 20 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 6d 2b 38 fa 48 8b 1b 48 85 db 74
RSP: 0018:ffffc90001b4fc18 EFLAGS: 00010a02
RAX: 1ff1100e7dfbf004 RBX: ff888073efdf8020 RCX: ffff88807569d4c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff888073efdf8000
RBP: ffffffff8b831668 R08: ffffffff88188e45 R09: ffffffff83f45a7b
R10: 0000000000000009 R11: ffff88807569d4c0 R12: dffffc0000000000
R13: 1ffffffff1b6b255 R14: ff888073efdf8000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9c00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000020000180 CR3: 0000000071785000 CR4: 00000000001506f0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
inet_ctl_sock_destroy include/net/inet_common.h:65 [inline]
tcp_sk_exit+0x19d/0x270 net/ipv4/tcp_ipv4.c:2839
ops_exit_list net/core/net_namespace.c:175 [inline]
cleanup_net+0x708/0xbd0 net/core/net_namespace.c:595
process_one_work+0x789/0xfd0 kernel/workqueue.c:2275
worker_thread+0xac1/0x1300 kernel/workqueue.c:2421
kthread+0x39a/0x3c0 kernel/kthread.c:292
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:294
Modules linked in:
---[ end trace d98924a1f9652506 ]---
RIP: 0010:__sock_release net/socket.c:594 [inline]
RIP: 0010:sock_release+0x24/0x140 net/socket.c:627
Code: f9 eb 8a 0f 1f 00 41 57 41 56 41 54 53 49 89 fe 49 bc 00 00 00 00 00 fc ff df e8 67 53 f4 f9 49 8d 5e 20 48 89 d8 48 c1 e8 03 <42> 80 3c 20 00 74 08 48 89 df e8 6d 2b 38 fa 48 8b 1b 48 85 db 74
RSP: 0018:ffffc90001b4fc18 EFLAGS: 00010a02
RAX: 1ff1100e7dfbf004 RBX: ff888073efdf8020 RCX: ffff88807569d4c0
RDX: 0000000000000000 RSI: 0000000000000001 RDI: ff888073efdf8000
RBP: ffffffff8b831668 R08: ffffffff88188e45 R09: ffffffff83f45a7b
R10: 0000000000000009 R11: ffff88807569d4c0 R12: dffffc0000000000
R13: 1ffffffff1b6b255 R14: ff888073efdf8000 R15: 0000000000000001
FS: 0000000000000000(0000) GS:ffff8880b9d00000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00005575e08092f0 CR3: 0000000078a63000 CR4: 00000000001506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400


---
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.

[syzbot]

Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.