[v5.15] INFO: task hung in process_measurement (3)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 16fdf2c7111b Linux 5.15.181
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=143438f4580000
kernel config: https://syzkaller.appspot.com/x/.config?x=1748ac0065c72647
dashboard link: https://syzkaller.appspot.com/bug?extid=7253e80eb0ac03a1ccda
compiler: Debian clang version 20.1.2 (++20250402124445+58df0ef89dd6-1~exp1~20250402004600.97), Debian LLD 20.1.2

Unfortunately, I don't have any reproducer for this issue yet.

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/d8540163643f/disk-16fdf2c7.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/1a4c570bb8bc/vmlinux-16fdf2c7.xz
kernel image: https://storage.googleapis.com/syzbot-assets/d4ed683eba5e/bzImage-16fdf2c7.xz

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7253e8...@syzkaller.appspotmail.com

INFO: task syz.3.123:5183 blocked for more than 143 seconds.
Not tainted 5.15.181-syzkaller #0
"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
task:syz.3.123 state:D stack:27632 pid: 5183 ppid: 4175 flags:0x00004004
Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
schedule+0x11b/0x1e0 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533
do_open fs/namei.c:3610 [inline]
path_openat+0x2735/0x2f30 fs/namei.c:3742
do_filp_open+0x1b3/0x3e0 fs/namei.c:3769
do_sys_openat2+0x142/0x4a0 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]
__do_sys_creat fs/open.c:1345 [inline]
__se_sys_creat fs/open.c:1339 [inline]
__x64_sys_creat+0x8c/0xb0 fs/open.c:1339
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0
RIP: 0033:0x7f164f4f2969
RSP: 002b:00007f164d339038 EFLAGS: 00000246 ORIG_RAX: 0000000000000055
RAX: ffffffffffffffda RBX: 00007f164f71a080 RCX: 00007f164f4f2969
RDX: 0000000000000000 RSI: d931d3864d39dcca RDI: 0000200000000100
RBP: 00007f164f574ab1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 0000000000000001 R14: 00007f164f71a080 R15: 00007fffb3db6308
</TASK>

Showing all locks held in the system:
1 lock held by khungtaskd/27:
#0: ffffffff8c11be60 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
4 locks held by kworker/u4:1/144:
#0: ffff888018d98938 ((wq_completion)writeback){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000166fd00 ((work_completion)(&(&wb->dwork)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff8880617d40e0 (&type->s_umount_key#55){++++}-{3:3}, at: trylock_super+0x1c/0xf0 fs/super.c:418
#3: ffff88802a5551b0 (&sbi->gc_lock){+.+.}-{3:3}, at: f2fs_balance_fs+0x47d/0x660 fs/f2fs/segment.c:528
2 locks held by getty/3933:
#0: ffff88807f091098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cd62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
2 locks held by kworker/0:6/4212:
#0: ffff888016872138 ((wq_completion)rcu_gp){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900030dfd00 ((work_completion)(&rew.rew_work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
7 locks held by syz.3.123/5146:
2 locks held by syz.3.123/5183:
#0: ffff8880617d4460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805e53ba50 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805e53ba50 (&sb->s_type->i_mutex_key#22){+.+.}-{3:3}, at: process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
1 lock held by syz.7.677/7683:
#0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
#0: ffff888074535c10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
1 lock held by dhcpcd/7737:
#0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
#0: ffff88801c260210 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
2 locks held by dhcpcd/7738:
#0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: __sock_release net/socket.c:648 [inline]
#0: ffff88801c260e10 (&sb->s_type->i_mutex_key#11){+.+.}-{3:3}, at: sock_close+0x90/0x240 net/socket.c:1336
#1: ffffffff8c1208e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: exp_funnel_lock kernel/rcu/tree_exp.h:322 [inline]
#1: ffffffff8c1208e8 (rcu_state.exp_mutex){+.+.}-{3:3}, at: synchronize_rcu_expedited+0x320/0x6b0 kernel/rcu/tree_exp.h:845

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

NMI backtrace for cpu 0
CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 4221 Comm: kworker/u4:5 Not tainted 5.15.181-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/19/2025
Workqueue: bat_events batadv_nc_worker
RIP: 0010:check_region_inline mm/kasan/generic.c:-1 [inline]
RIP: 0010:kasan_check_range+0x30/0x290 mm/kasan/generic.c:189
Code: 84 a4 01 00 00 41 57 41 56 53 49 89 f8 49 01 f0 0f 82 57 02 00 00 49 89 f8 49 c1 e8 2f 41 81 f8 ff ff 01 00 0f 82 43 02 00 00 <49> bf 01 00 00 00 00 fc ff df 49 89 fb 49 c1 eb 03 49 b8 00 00 00
RSP: 0018:ffffc9000316f800 EFLAGS: 00000046
RAX: 0000000000000001 RBX: 0000000000000015 RCX: ffffffff815bf989
RDX: 0000000000000000 RSI: 0000000000000008 RDI: ffffffff8ff990c0
RBP: ffffc9000316fa70 R08: 000000000001ffff R09: fffffbfff1ff3236
R10: fffffbfff1ff3236 R11: 1ffffffff1ff3235 R12: 00000000ac97705a
R13: ffff888029d49dc0 R14: 00000000583408ea R15: ffff888029d4a920
FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f6cafb1eab8 CR3: 0000000028a2e000 CR4: 00000000003506e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>
instrument_atomic_read include/linux/instrumented.h:71 [inline]
test_bit include/asm-generic/bitops/instrumented-non-atomic.h:134 [inline]
hlock_class kernel/locking/lockdep.c:197 [inline]
__lock_acquire+0x12d9/0x7c60 kernel/locking/lockdep.c:5009
lock_acquire+0x197/0x3f0 kernel/locking/lockdep.c:5623
rcu_lock_acquire+0x2a/0x30 include/linux/rcupdate.h:312
rcu_read_lock include/linux/rcupdate.h:739 [inline]
batadv_nc_purge_orig_hash net/batman-adv/network-coding.c:412 [inline]
batadv_nc_worker+0xc9/0x5c0 net/batman-adv/network-coding.c:723
process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</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.

If the report is already addressed, let syzbot know by replying with:
#syz fix: exact-commit-title

If you want to overwrite report's subsystems, reply with:
#syz set subsystems: new-subsystem
(See the list of subsystem names on the web dashboard)

If the report is a duplicate of another one, reply with:
#syz dup: exact-subject-of-another-report

If you want to undo deduplication, reply with:
#syz undup

[syzbot]

syzbot has found a reproducer for the following issue on:

HEAD commit: c79648372d02 Linux 5.15.189
git tree: linux-5.15.y
console output: https://syzkaller.appspot.com/x/log.txt?x=124cf434580000
kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=7253e80eb0ac03a1ccda
compiler: Debian clang version 20.1.7 (++20250616065708+6146a88f6049-1~exp1~20250616065826.132), Debian LLD 20.1.7
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b1f9a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b1f9a2580000

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/fa511d2a8893/disk-c7964837.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/f14b6c77bbb9/vmlinux-c7964837.xz
kernel image: https://storage.googleapis.com/syzbot-assets/388987ba15c6/bzImage-c7964837.xz
mounted in repro: https://storage.googleapis.com/syzbot-assets/5381c2bbfb8d/mount_0.gz
fsck result: failed (log: https://syzkaller.appspot.com/x/fsck.log?x=144cf434580000)

IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+7253e8...@syzkaller.appspotmail.com

INFO: task syz.4.29:4427 blocked for more than 143 seconds.
Not tainted 5.15.189-syzkaller #0

"echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.

task:syz.4.29 state:D stack:25360 pid: 4427 ppid: 4311 flags:0x00004004

Call Trace:
<TASK>
context_switch kernel/sched/core.c:5030 [inline]
__schedule+0x11b8/0x43b0 kernel/sched/core.c:6376
schedule+0x11b/0x1e0 kernel/sched/core.c:6459
rwsem_down_write_slowpath+0xc46/0x11f0 kernel/locking/rwsem.c:1165
inode_lock include/linux/fs.h:787 [inline]
process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
ima_file_check+0xc1/0x100 security/integrity/ima/ima_main.c:533
do_open fs/namei.c:3610 [inline]
path_openat+0x2735/0x2f30 fs/namei.c:3742
do_filp_open+0x1b3/0x3e0 fs/namei.c:3769
do_sys_openat2+0x142/0x4a0 fs/open.c:1253
do_sys_open fs/open.c:1269 [inline]

__do_sys_openat fs/open.c:1285 [inline]
__se_sys_openat fs/open.c:1280 [inline]
__x64_sys_openat+0x135/0x160 fs/open.c:1280

do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x4c/0xa0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x66/0xd0

RIP: 0033:0x7f50de68abe9
RSP: 002b:00007f50ddcfa038 EFLAGS: 00000246 ORIG_RAX: 0000000000000101
RAX: ffffffffffffffda RBX: 00007f50de8b1fa0 RCX: 00007f50de68abe9
RDX: 0000000000103a42 RSI: 0000200000000440 RDI: ffffffffffffff9c
RBP: 00007f50de70de19 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000100 R11: 0000000000000246 R12: 0000000000000000
R13: 00007f50de8b2038 R14: 00007f50de8b1fa0 R15: 00007fff496696c8

</TASK>

Showing all locks held in the system:

4 locks held by kworker/1:0/21:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90000db7d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff8880223980e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888058b27090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27

1 lock held by khungtaskd/27:

#0: ffffffff8c11c360 (rcu_read_lock){....}-{1:2}, at: rcu_lock_acquire+0x0/0x30
3 locks held by kworker/u4:3/894:
2 locks held by kworker/1:2/1108:
4 locks held by kworker/0:2/1325:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc90005267d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff8880756820e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888021457090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:3/1336:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900051d7d00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88805888c0e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888079aec090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
2 locks held by getty/3958:
#0: ffff88802b98c098 (&tty->ldisc_sem){++++}-{0:0}, at: tty_ldisc_ref_wait+0x21/0x70 drivers/tty/tty_ldisc.c:252
#1: ffffc90002cf62e8 (&ldata->atomic_read_lock){+.+.}-{3:3}, at: n_tty_read+0x5ba/0x1a30 drivers/tty/n_tty.c:2158
4 locks held by kworker/1:4/4249:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000111fd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88802b3b80e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff88802476f090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:11/4281:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900034afd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88807dd820e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888058b4d090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:12/4282:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900034bfd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88807a51e0e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff88805d4a3090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:13/4283:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900034cfd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff888078b240e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888023240090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:14/4284:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc900034efd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88801f4840e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff888076d7e090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/0:16/4286:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000350fd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff8880565f80e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff88807765f090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
4 locks held by kworker/1:6/4369:
#0: ffff888016871138 ((wq_completion)events_long){+.+.}-{0:0}, at: process_one_work+0x760/0x1000 kernel/workqueue.c:-1
#1: ffffc9000427fd00 ((work_completion)(&(&sbi->old_work)->work)){+.+.}-{0:0}, at: process_one_work+0x7a3/0x1000 kernel/workqueue.c:2285
#2: ffff88814ca0e0e0 (&type->s_umount_key#53){++++}-{3:3}, at: flush_old_commits+0xc8/0x2f0 fs/reiserfs/super.c:97
#3: ffff88807a3ba090 (&sbi->lock){+.+.}-{3:3}, at: reiserfs_write_lock+0x75/0xd0 fs/reiserfs/lock.c:27
2 locks held by syz.4.29/4427:
#0: ffff88802b3b8460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805ad0c520 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805ad0c520 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
3 locks held by syz.4.29/4435:
3 locks held by syz.3.20/4460:
2 locks held by syz.0.35/4462:
#0: ffff88805888c460 (sb_writers#13){.+.+}-{0:0}, at: mnt_want_write+0x3d/0x90 fs/namespace.c:377
#1: ffff88805adfd260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: inode_lock include/linux/fs.h:787 [inline]
#1: ffff88805adfd260 (&sb->s_type->i_mutex_key#21){+.+.}-{3:3}, at: process_measurement+0x33d/0x1a10 security/integrity/ima/ima_main.c:242
3 locks held by syz.0.35/4470:
3 locks held by syz.1.36/4471:
3 locks held by syz.2.38/4475:
3 locks held by syz.5.45/4551:
2 locks held by udevd/4640:
3 locks held by syz.9.43/4657:
3 locks held by syz.8.51/4662:
3 locks held by syz.7.54/4680:
3 locks held by syz.6.58/4705:
2 locks held by syz.1.294/5479:
2 locks held by syz.0.293/5478:
#0: ffff8880b913a318 (&rq->__lock){-.-.}-{2:2}, at: raw_spin_rq_lock_nested+0x26/0x140 kernel/sched/core.c:475
#1: ffff8880b9127848 (&per_cpu_ptr(group->pcpu, cpu)->seq){-.-.}-{0:0}, at: psi_task_switch+0x4d6/0x810 kernel/sched/psi.c:891
2 locks held by syz.3.295/5482:
1 lock held by syz.2.296/5485:
1 lock held by syz.2.296/5490:
1 lock held by syz.4.297/5487:

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

NMI backtrace for cpu 0

CPU: 0 PID: 27 Comm: khungtaskd Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025

Call Trace:
<TASK>
dump_stack_lvl+0x168/0x230 lib/dump_stack.c:106
nmi_cpu_backtrace+0x397/0x3d0 lib/nmi_backtrace.c:111
nmi_trigger_cpumask_backtrace+0x163/0x280 lib/nmi_backtrace.c:62
trigger_all_cpu_backtrace include/linux/nmi.h:148 [inline]
check_hung_uninterruptible_tasks kernel/hung_task.c:212 [inline]
watchdog+0xe0f/0xe50 kernel/hung_task.c:369
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1

CPU: 1 PID: 9 Comm: kworker/u4:0 Not tainted 5.15.189-syzkaller #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/12/2025
Workqueue: phy12 ieee80211_iface_work
RIP: 0010:get_current arch/x86/include/asm/current.h:15 [inline]
RIP: 0010:__sanitizer_cov_trace_pc+0x4/0x60 kernel/kcov.c:205
Code: 84 00 00 00 00 00 53 48 89 fb e8 17 00 00 00 48 8b 3d c0 ac f1 0b 48 89 de 5b e9 77 99 43 00 00 00 cc cc 00 00 cc 48 8b 04 24 <65> 48 8b 0d 94 ab 8a 7e 65 8b 15 95 ab 8a 7e 81 e2 00 01 ff 00 74
RSP: 0018:ffffc90000ce78f0 EFLAGS: 00000206
RAX: ffffffff893eb94b RBX: 0000000000000006 RCX: ffff88813fed0000
RDX: 0000000000000000 RSI: 0000000000000006 RDI: 0000000000000040
RBP: 0000000000000078 R08: dffffc0000000000 R09: fffffbfff1ad2dd6
R10: fffffbfff1ad2dd6 R11: 1ffffffff1ad2dd5 R12: 000000000000000b
R13: 0000000000000078 R14: dffffc0000000000 R15: ffff88805cd13350

FS: 0000000000000000(0000) GS:ffff8880b9100000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033

CR2: 00007fc478193000 CR3: 000000001e181000 CR4: 00000000003506e0

DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
Call Trace:
<TASK>

ieee80211_sta_get_rates+0x39b/0x6b0 net/mac80211/util.c:2128
ieee80211_update_sta_info net/mac80211/ibss.c:1007 [inline]
ieee80211_rx_bss_info net/mac80211/ibss.c:1121 [inline]
ieee80211_rx_mgmt_probe_beacon net/mac80211/ibss.c:1614 [inline]
ieee80211_ibss_rx_queued_mgmt+0xf47/0x29c0 net/mac80211/ibss.c:1643
ieee80211_iface_process_skb net/mac80211/iface.c:1459 [inline]
ieee80211_iface_work+0x70e/0xc60 net/mac80211/iface.c:1513

process_one_work+0x863/0x1000 kernel/workqueue.c:2310
worker_thread+0xaa8/0x12a0 kernel/workqueue.c:2457
kthread+0x436/0x520 kernel/kthread.c:334
ret_from_fork+0x1f/0x30 arch/x86/entry/entry_64.S:287
</TASK>


---

If you want syzbot to run the reproducer, reply with:
#syz test: git://repo/address.git branch-or-commit-hash
If you attach or paste a git patch, syzbot will apply it before testing.

[syzbot]

syzbot suspects this issue could be fixed by backporting the following commit:

commit fb6f20ecb121cef4d7946f834a6ee867c4e21b4a
git tree: upstream
Author: Jan Kara <ja...@suse.cz>
Date: Thu Oct 17 10:28:23 2024 +0000

reiserfs: The last commit

bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17079eb4580000

kernel config: https://syzkaller.appspot.com/x/.config?x=f3b1215b3cf4119f
dashboard link: https://syzkaller.appspot.com/bug?extid=7253e80eb0ac03a1ccda

syz repro: https://syzkaller.appspot.com/x/repro.syz?x=10b1f9a2580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=14b1f9a2580000

Please keep in mind that other backports might be required as well.

For information about bisection process see: https://goo.gl/tpsmEJ#bisection