INFO: task hung in process_measurement

6 views
Skip to first unread message

syzbot

unread,
Jan 18, 2020, 9:28:09 PM1/18/20
to syzkaller...@googlegroups.com
Hello,

syzbot found the following crash on:

HEAD commit: c1141b3a Linux 4.14.166
git tree: linux-4.14.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11504966e00000
kernel config: https://syzkaller.appspot.com/x/.config?x=a99b4b74c4c01851
dashboard link: https://syzkaller.appspot.com/bug?extid=f229a5a31129665e9808
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+f229a5...@syzkaller.appspotmail.com

INFO: task syz-executor.2:21831 blocked for more than 140 seconds.
Not tainted 4.14.166-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.2 D28320 21831 7273 0x00000004
Call Trace:
context_switch kernel/sched/core.c:2808 [inline]
__schedule+0x7b8/0x1cd0 kernel/sched/core.c:3384
schedule+0x92/0x1c0 kernel/sched/core.c:3428
__rwsem_down_write_failed_common kernel/locking/rwsem-xadd.c:588 [inline]
rwsem_down_write_failed+0x5ce/0xb50 kernel/locking/rwsem-xadd.c:617
call_rwsem_down_write_failed+0x17/0x30 arch/x86/lib/rwsem.S:105
__down_write arch/x86/include/asm/rwsem.h:126 [inline]
down_write+0x53/0x90 kernel/locking/rwsem.c:56
inode_lock include/linux/fs.h:718 [inline]
process_measurement+0xb2b/0xb80 security/integrity/ima/ima_main.c:206
ima_file_check+0x30/0x40 security/integrity/ima/ima_main.c:353
do_last fs/namei.c:3432 [inline]
path_openat+0x1626/0x3f70 fs/namei.c:3566


---
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 syzk...@googlegroups.com.

syzbot will keep track of this bug report. See:
https://goo.gl/tpsmEJ#status for how to communicate with syzbot.

syzbot

unread,
Jul 12, 2020, 8:59:17 PM7/12/20
to syzkaller...@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