INFO: task hung in process_measurement (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: ad326970 Linux 4.19.152
git tree: linux-4.19.y
console output: https://syzkaller.appspot.com/x/log.txt?x=11ae1850500000
kernel config: https://syzkaller.appspot.com/x/.config?x=1ec7667b405157e
dashboard link: https://syzkaller.appspot.com/bug?extid=0145eac573a3198ccca3
compiler: gcc (GCC) 10.1.0-syz 20200507

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+0145ea...@syzkaller.appspotmail.com

INFO: task syz-executor.1:20133 blocked for more than 140 seconds.
Not tainted 4.19.152-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
syz-executor.1 D29184 20133 8118 0x00000000
Call Trace:
context_switch kernel/sched/core.c:2828 [inline]
__schedule+0x887/0x2040 kernel/sched/core.c:3517
schedule+0x8d/0x1b0 kernel/sched/core.c:3561
schedule_preempt_disabled+0xf/0x20 kernel/sched/core.c:3619
__mutex_lock_common kernel/locking/mutex.c:1002 [inline]
__mutex_lock+0x647/0x1260 kernel/locking/mutex.c:1072
process_measurement+0x316/0x1440 security/integrity/ima/ima_main.c:224
ima_file_check+0xb9/0x100 security/integrity/ima/ima_main.c:391
do_last fs/namei.c:3425 [inline]
path_openat+0x7e4/0x2df0 fs/namei.c:3537
do_filp_open+0x18c/0x3f0 fs/namei.c:3567
do_sys_open+0x3b3/0x520 fs/open.c:1085
do_syscall_64+0xf9/0x620 arch/x86/entry/common.c:293
entry_SYSCALL_64_after_hwframe+0x49/0xbe
RIP: 0033:0x45de59
Code: 0d b4 fb ff c3 66 2e 0f 1f 84 00 00 00 00 00 66 90 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 0f 83 db b3 fb ff c3 66 2e 0f 1f 84 00 00 00 00
RSP: 002b:00007f3abdb12c78 EFLAGS: 00000246 ORIG_RAX: 0000000000000002
RAX: ffffffffffffffda RBX: 0000000000022140 RCX: 000000000045de59
RDX: 0000000000000000 RSI: 0000000000141042 RDI: 0000000020000100
RBP: 000000000118c0b0 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 000000000118c07c
R13: 00007ffcef627e9f R14: 00007f3abdb139c0 R15: 000000000118c07c

Showing all locks held in the system:
1 lock held by khungtaskd/1566:
#0: 0000000000302253 (rcu_read_lock){....}, at: debug_show_all_locks+0x53/0x265 kernel/locking/lockdep.c:4440
1 lock held by in:imklog/7736:
#0: 00000000b8723f59 (&f->f_pos_lock){+.+.}, at: __fdget_pos+0x26f/0x310 fs/file.c:767
2 locks held by agetty/7761:
#0: 00000000f6224f04 (&tty->ldisc_sem){++++}, at: tty_ldisc_ref_wait+0x22/0x80 drivers/tty/tty_ldisc.c:272
#1: 00000000dccf2228 (&ldata->atomic_read_lock){+.+.}, at: n_tty_read+0x217/0x1950 drivers/tty/n_tty.c:2154
1 lock held by syz-executor.1/20117:
1 lock held by syz-executor.1/20133:
#0: 000000005c54ec2b (&iint->mutex){+.+.}, at: process_measurement+0x316/0x1440 security/integrity/ima/ima_main.c:224
1 lock held by syz-executor.1/20479:
1 lock held by syz-executor.1/23755:

=============================================

NMI backtrace for cpu 0
CPU: 0 PID: 1566 Comm: khungtaskd Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
Call Trace:
__dump_stack lib/dump_stack.c:77 [inline]
dump_stack+0x1fc/0x2fe lib/dump_stack.c:118
nmi_cpu_backtrace.cold+0x63/0xa2 lib/nmi_backtrace.c:101
nmi_trigger_cpumask_backtrace+0x1a6/0x1eb lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:146 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:203 [inline]
watchdog+0x991/0xe60 kernel/hung_task.c:287
kthread+0x33f/0x460 kernel/kthread.c:259
ret_from_fork+0x24/0x30 arch/x86/entry/entry_64.S:415
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 20117 Comm: syz-executor.1 Not tainted 4.19.152-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 01/01/2011
RIP: 0010:loop1+0x7a9/0x892
Code: 43 7b f0 ea 19 03 5c 3c 68 c5 e5 73 d2 13 c4 43 7b f0 f2 0b 09 d6 45 89 df 41 31 c7 c4 63 7b f0 e1 0d 45 31 f5 c5 ed 73 d2 11 <45> 21 d7 c4 43 7b f0 f2 06 c5 ed ef d3 41 01 d9 44 21 c6 45 31 f5
RSP: 0018:ffff88804f067300 EFLAGS: 00000202
RAX: 00000000d8068b60 RBX: 000000000313845f RCX: 00000000bdd864ce
RDX: 000000000d898ddb RSI: 00000000bdd9eddf RDI: 0000000000000100
RBP: ffff88804f067600 R08: 0000000027c93f23 R09: 0000000049351a6d
R10: 000000008d6fe70a R11: 0000000002e39b70 R12: 000000002675eec3
R13: 0000000056a228ba R14: 00000000e151adfc R15: 00000000dae51010
FS: 00007f3abdb55700(0000) GS:ffff8880ba100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000001bcca98 CR3: 00000000597b4000 CR4: 00000000001406e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:


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