INFO: task can't die in __might_resched

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 60e8840126bd Add linux-next specific files for 20211018
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=134be130b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=4bd44cafcda7632e
dashboard link: https://syzkaller.appspot.com/bug?extid=956e07db354b858e5982
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [da...@davemloft.net dsa...@kernel.org ku...@kernel.org linux-...@vger.kernel.org net...@vger.kernel.org yosh...@linux-ipv6.org]

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+956e07...@syzkaller.appspotmail.com

INFO: task syz-executor.0:26247 can't die for more than 143 seconds.
task:syz-executor.0 state:R running task stack:27016 pid:26247 ppid: 11600 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:4965 [inline]
__schedule+0xa9a/0x4940 kernel/sched/core.c:6246
lock_is_held include/linux/lockdep.h:283 [inline]
__might_resched+0x21/0x2c0 kernel/sched/core.c:9495
</TASK>
INFO: task syz-executor.4:26248 can't die for more than 147 seconds.
task:syz-executor.4 state:R running task stack:26952 pid:26248 ppid: 6576 flags:0x00004006
Call Trace:
<TASK>
</TASK>
INFO: task syz-executor.2:26252 can't die for more than 152 seconds.
task:syz-executor.2 state:R running task stack:27808 pid:26252 ppid: 6567 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:4965 [inline]
__schedule+0xa9a/0x4940 kernel/sched/core.c:6246
preempt_schedule_common+0x45/0xc0 kernel/sched/core.c:6412
__cond_resched+0x13/0x20 kernel/sched/core.c:8125
_cond_resched include/linux/sched.h:2027 [inline]
inet_twsk_purge+0xed/0x7d0 net/ipv4/inet_timewait_sock.c:267
ops_exit_list+0x10d/0x160 net/core/net_namespace.c:171
setup_net+0x639/0xa30 net/core/net_namespace.c:349
copy_net_ns+0x318/0x760 net/core/net_namespace.c:470
create_new_namespaces+0x3f6/0xb20 kernel/nsproxy.c:110
unshare_nsproxy_namespaces+0xc1/0x1f0 kernel/nsproxy.c:226
ksys_unshare+0x445/0x920 kernel/fork.c:3125
__do_sys_unshare kernel/fork.c:3196 [inline]
__se_sys_unshare kernel/fork.c:3194 [inline]
__x64_sys_unshare+0x2d/0x40 kernel/fork.c:3194
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x35/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x44/0xae
RIP: 0033:0x7fb253f81a39
RSP: 002b:00007fb2514b5188 EFLAGS: 00000246 ORIG_RAX: 0000000000000110
RAX: ffffffffffffffda RBX: 00007fb2540850e0 RCX: 00007fb253f81a39
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000040000000
RBP: 00007fb253fdbc5f R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fffe0693d6f R14: 00007fb2514b5300 R15: 0000000000022000
</TASK>


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