INFO: task can't die in mark_held_locks (2)

4 views
Skip to first unread message

syzbot

unread,
Dec 13, 2021, 8:28:32 AM12/13/21
to syzkaller-upst...@googlegroups.com
Hello,

syzbot found the following issue on:

HEAD commit: 4eee8d0b64ec Add linux-next specific files for 20211208
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=1152dce1b00000
kernel config: https://syzkaller.appspot.com/x/.config?x=20b74d9da4ce1ef1
dashboard link: https://syzkaller.appspot.com/bug?extid=88392dd280b06d8f0357
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [bri...@redhat.com bse...@google.com chri...@brauner.io dietmar....@arm.com juri....@redhat.com linux-...@vger.kernel.org mgo...@suse.de mi...@redhat.com pet...@infradead.org ros...@goodmis.org vincent...@linaro.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+88392d...@syzkaller.appspotmail.com

INFO: task syz-executor.4:8979 can't die for more than 143 seconds.
task:syz-executor.4 state:R running task stack:25128 pid: 8979 ppid: 6535 flags:0x00004006
Call Trace:
<TASK>
context_switch kernel/sched/core.c:4986 [inline]
__schedule+0xab2/0x4d90 kernel/sched/core.c:6296
mark_held_locks+0x9f/0xe0 kernel/locking/lockdep.c:4206
</TASK>
INFO: task syz-executor.2:8973 can't die for more than 148 seconds.
task:syz-executor.2 state:R running task stack:25624 pid: 8973 ppid: 6534 flags:0x00004006
Call Trace:
<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

unread,
Apr 10, 2022, 10:18:18 AM4/10/22
to syzkaller-upst...@googlegroups.com
Auto-closing this bug as obsolete.
Crashes did not happen for a while, no reproducer and no activity.
Reply all
Reply to author
Forward
0 new messages