[syzbot] [kernel?] WARNING in update_rq_clock (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 8b69c0475871 Merge tag 'input-for-v7.2-rc0-2' of git://git..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=1196f4ea580000
kernel config: https://syzkaller.appspot.com/x/.config?x=eb3cf873145f98c4
dashboard link: https://syzkaller.appspot.com/bug?extid=681e729b2cf0d4860042
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6fbba2b94559/disk-8b69c047.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/377e82061e2d/vmlinux-8b69c047.xz
kernel image: https://storage.googleapis.com/syzbot-assets/f299b46fb771/bzImage-8b69c047.xz

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

------------[ cut here ]------------
debug_locks && !(lock_is_held(&(__rq_lockp(rq))->dep_map) != 0)
WARNING: kernel/sched/sched.h:1641 at lockdep_assert_rq_held kernel/sched/sched.h:1641 [inline], CPU#0: syz.4.1183/11558
WARNING: kernel/sched/sched.h:1641 at lockdep_assert_rq_held kernel/sched/sched.h:1638 [inline], CPU#0: syz.4.1183/11558
WARNING: kernel/sched/sched.h:1641 at update_rq_clock+0x40a/0xd20 kernel/sched/core.c:865, CPU#0: syz.4.1183/11558
Modules linked in:
CPU: 0 UID: 0 PID: 11558 Comm: syz.4.1183 Tainted: G U L syzkaller #0 PREEMPT(full)
Tainted: [U]=USER, [L]=SOFTLOCKUP
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 05/09/2026
RIP: 0010:lockdep_assert_rq_held kernel/sched/sched.h:1641 [inline]
RIP: 0010:lockdep_assert_rq_held kernel/sched/sched.h:1638 [inline]
RIP: 0010:update_rq_clock+0x40a/0xd20 kernel/sched/core.c:865
Code: ab c8 0b 00 00 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f e9 d8 7e c8 09 a8 04 0f 84 df fc ff ff 90 0f 0b 90 e9 d6 fc ff ff 90 <0f> 0b 90 e9 92 fc ff ff 4c 8d 83 c0 0b 00 00 48 b8 00 00 00 00 00
RSP: 0018:ffffc90003cb70b8 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff8880b853b600 RCX: 0000000000000001
RDX: 0000000000000046 RSI: ffffffff8df333b0 RDI: ffffffff8c1e8f80
RBP: ffffc90003cb7260 R08: 0000000000000001 R09: 0000000000000001
R10: ffffffff90dbdb97 R11: 0000000000000000 R12: ffffffff90dc0f44
R13: ffff8880b853c4e0 R14: ffff88801e6a1f00 R15: ffff8880b843c198
FS: 00007fece89b36c0(0000) GS:ffff8881242e7000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000000 CR3: 00000000775a2000 CR4: 00000000003526f0
Call Trace:
<TASK>
pick_next_task kernel/sched/core.c:6338 [inline]
__schedule+0x1e2d/0x6730 kernel/sched/core.c:7149
preempt_schedule_common+0x42/0xc0 kernel/sched/core.c:7413
preempt_schedule_thunk+0x16/0x40 arch/x86/entry/thunk.S:12
__local_bh_enable_ip+0xff/0x120 kernel/softirq.c:457
local_bh_enable include/linux/bottom_half.h:33 [inline]
fpregs_unlock arch/x86/include/asm/fpu/api.h:77 [inline]
kernel_fpu_end arch/x86/kernel/fpu/core.c:506 [inline]
kernel_fpu_end+0x64/0x80 arch/x86/kernel/fpu/core.c:499
sha256_blocks_avx2+0x4e/0x90 lib/crypto/x86/sha256.h:31
sha256_blocks lib/crypto/x86/sha256.h:58 [inline]
__sha256_update+0x188/0x1c0 lib/crypto/sha256.c:208
crypto_sha256_update+0x23/0x30 crypto/sha256.c:142
crypto_shash_finup+0x34b/0x6b0 crypto/shash.c:123
crypto_shash_update include/crypto/hash.h:998 [inline]
ima_calc_file_hash_tfm+0x299/0x350 security/integrity/ima/ima_crypto.c:233
ima_calc_file_hash+0x1e3/0x380 security/integrity/ima/ima_crypto.c:280
ima_collect_measurement+0x94f/0xb30 security/integrity/ima/ima_api.c:300
process_measurement+0xdfe/0x2350 security/integrity/ima/ima_main.c:425
ima_file_mmap+0x1c4/0x1f0 security/integrity/ima/ima_main.c:523
security_mmap_file+0x278/0x9b0 security/security.c:2581
vm_mmap_pgoff+0xec/0x470 mm/util.c:575
ksys_mmap_pgoff+0x285/0x610 mm/mmap.c:606
__do_sys_mmap arch/x86/kernel/sys_x86_64.c:89 [inline]
__se_sys_mmap arch/x86/kernel/sys_x86_64.c:82 [inline]
__x64_sys_mmap+0x125/0x190 arch/x86/kernel/sys_x86_64.c:82
do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline]
do_syscall_64+0x115/0x840 arch/x86/entry/syscall_64.c:94
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fece7b9ce59
Code: ff c3 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 44 00 00 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 73 01 c3 48 c7 c1 e8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fece89b3028 EFLAGS: 00000246 ORIG_RAX: 0000000000000009
RAX: ffffffffffffffda RBX: 00007fece7e16090 RCX: 00007fece7b9ce59
RDX: 00004000000000df RSI: 200000000000000b RDI: 0000000000000000
RBP: 00007fece7c32e6f R08: 0000000000000401 R09: 0000300000000000
R10: 0000000000040eb1 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fece7e16128 R14: 00007fece7e16090 R15: 00007ffd39c61db8
</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