* [syzbot] [kernel?] WARNING in update_rq_clock (2)
@ 2026-07-03 0:38 syzbot
2026-07-03 9:39 ` Thomas Gleixner
2026-08-03 6:40 ` [syzbot] [mm?] " syzbot
0 siblings, 2 replies; 5+ messages in thread
From: syzbot @ 2026-07-03 0:38 UTC (permalink / raw)
To: bp, dave.hansen, hpa, linux-kernel, mingo, syzkaller-bugs, tglx,
x86
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+681e729b2cf0d4860042@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 syzkaller@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [kernel?] WARNING in update_rq_clock (2)
2026-07-03 0:38 [syzbot] [kernel?] WARNING in update_rq_clock (2) syzbot
@ 2026-07-03 9:39 ` Thomas Gleixner
2026-07-03 9:48 ` Peter Zijlstra
2026-07-03 10:08 ` Aleksandr Nogikh
2026-08-03 6:40 ` [syzbot] [mm?] " syzbot
1 sibling, 2 replies; 5+ messages in thread
From: Thomas Gleixner @ 2026-07-03 9:39 UTC (permalink / raw)
To: syzbot, bp, dave.hansen, hpa, linux-kernel, mingo, syzkaller-bugs,
x86
Cc: Peter Zijlstra
On Thu, Jul 02 2026 at 17:38, syzbot wrote:
CC+: Peter
Dear syzbot folks. The selection of people you CC on your reports is
annoyingly random. The splat clearly says:
> WARNING: kernel/sched/sched.h:1641 at lockdep_assert_rq_held kernel/sched/sched.h:1641 [inline], CPU#0: syz.4.1183/11558
So why not picking that up and:
# scripts/get_maintainer.pl -f kernel/sched/sched.h
Ingo Molnar <mingo@redhat.com> (maintainer:SCHEDULER)
Peter Zijlstra <peterz@infradead.org> (maintainer:SCHEDULER)
Juri Lelli <juri.lelli@redhat.com> (maintainer:SCHEDULER)
Vincent Guittot <vincent.guittot@linaro.org> (maintainer:SCHEDULER)
Dietmar Eggemann <dietmar.eggemann@arm.com> (reviewer:SCHEDULER)
Steven Rostedt <rostedt@goodmis.org> (reviewer:SCHEDULER)
Ben Segall <bsegall@google.com> (reviewer:SCHEDULER)
Mel Gorman <mgorman@suse.de> (reviewer:SCHEDULER)
Valentin Schneider <vschneid@redhat.com> (reviewer:SCHEDULER)
K Prateek Nayak <kprateek.nayak@amd.com> (reviewer:SCHEDULER)
linux-kernel@vger.kernel.org (open list:SCHEDULER)
?
Leaving the report untrimmed for Peter.
> 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+681e729b2cf0d4860042@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 syzkaller@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [kernel?] WARNING in update_rq_clock (2)
2026-07-03 9:39 ` Thomas Gleixner
@ 2026-07-03 9:48 ` Peter Zijlstra
2026-07-03 10:08 ` Aleksandr Nogikh
1 sibling, 0 replies; 5+ messages in thread
From: Peter Zijlstra @ 2026-07-03 9:48 UTC (permalink / raw)
To: Thomas Gleixner
Cc: syzbot, bp, dave.hansen, hpa, linux-kernel, mingo, syzkaller-bugs,
x86
On Fri, Jul 03, 2026 at 11:39:38AM +0200, Thomas Gleixner wrote:
> On Thu, Jul 02 2026 at 17:38, syzbot wrote:
>
> CC+: Peter
>
> Dear syzbot folks. The selection of people you CC on your reports is
> annoyingly random. The splat clearly says:
>
> > WARNING: kernel/sched/sched.h:1641 at lockdep_assert_rq_held kernel/sched/sched.h:1641 [inline], CPU#0: syz.4.1183/11558
>
> So why not picking that up and:
>
> # scripts/get_maintainer.pl -f kernel/sched/sched.h
>
> Ingo Molnar <mingo@redhat.com> (maintainer:SCHEDULER)
> Peter Zijlstra <peterz@infradead.org> (maintainer:SCHEDULER)
> Juri Lelli <juri.lelli@redhat.com> (maintainer:SCHEDULER)
> Vincent Guittot <vincent.guittot@linaro.org> (maintainer:SCHEDULER)
> Dietmar Eggemann <dietmar.eggemann@arm.com> (reviewer:SCHEDULER)
> Steven Rostedt <rostedt@goodmis.org> (reviewer:SCHEDULER)
> Ben Segall <bsegall@google.com> (reviewer:SCHEDULER)
> Mel Gorman <mgorman@suse.de> (reviewer:SCHEDULER)
> Valentin Schneider <vschneid@redhat.com> (reviewer:SCHEDULER)
> K Prateek Nayak <kprateek.nayak@amd.com> (reviewer:SCHEDULER)
> linux-kernel@vger.kernel.org (open list:SCHEDULER)
>
>
> ?
>
> Leaving the report untrimmed for Peter.
>
> > 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+681e729b2cf0d4860042@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
This doesn't really make sense, this is in SCHED_CORE's pick_next_task()
restart_multi: loop. It does update_rq_clock() for all 'other' SMT
siblings, and validates __rq_lockp(rq) is held, which it very much
should be there.
Given you don't have a reproducer, and the static lock context analysis
code isn't complaining here, I'm rather suspect of the report and would
not rule out random memory corruption.
Anyway, if this persists and or a reproducer is found, I'm sure I'll
look at it eventually.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [kernel?] WARNING in update_rq_clock (2)
2026-07-03 9:39 ` Thomas Gleixner
2026-07-03 9:48 ` Peter Zijlstra
@ 2026-07-03 10:08 ` Aleksandr Nogikh
1 sibling, 0 replies; 5+ messages in thread
From: Aleksandr Nogikh @ 2026-07-03 10:08 UTC (permalink / raw)
To: Thomas Gleixner
Cc: syzbot, bp, dave.hansen, hpa, linux-kernel, mingo, syzkaller-bugs,
x86, Peter Zijlstra
Hi Thomas,
Thanks for reaching out!
On Fri, Jul 3, 2026 at 11:39 AM 'Thomas Gleixner' via syzkaller-bugs
<syzkaller-bugs@googlegroups.com> wrote:
>
> On Thu, Jul 02 2026 at 17:38, syzbot wrote:
>
> CC+: Peter
>
> Dear syzbot folks. The selection of people you CC on your reports is
> annoyingly random. The splat clearly says:
>
> > WARNING: kernel/sched/sched.h:1641 at lockdep_assert_rq_held kernel/sched/sched.h:1641 [inline], CPU#0: syz.4.1183/11558
>
> So why not picking that up and:
>
> # scripts/get_maintainer.pl -f kernel/sched/sched.h
In this case, syzkaller skipped `kernel/sched/sched.h` as being too
generic (usually the problems are not there) and focused on
`arch/x86/kernel/fpu/core.c` instead, for which get_maintianer.pl
gives exactly the Cc list we got.
I've filed https://github.com/google/syzkaller/issues/7563 to discuss
what we can change here.
--
Aleksandr
>
> Ingo Molnar <mingo@redhat.com> (maintainer:SCHEDULER)
> Peter Zijlstra <peterz@infradead.org> (maintainer:SCHEDULER)
> Juri Lelli <juri.lelli@redhat.com> (maintainer:SCHEDULER)
> Vincent Guittot <vincent.guittot@linaro.org> (maintainer:SCHEDULER)
> Dietmar Eggemann <dietmar.eggemann@arm.com> (reviewer:SCHEDULER)
> Steven Rostedt <rostedt@goodmis.org> (reviewer:SCHEDULER)
> Ben Segall <bsegall@google.com> (reviewer:SCHEDULER)
> Mel Gorman <mgorman@suse.de> (reviewer:SCHEDULER)
> Valentin Schneider <vschneid@redhat.com> (reviewer:SCHEDULER)
> K Prateek Nayak <kprateek.nayak@amd.com> (reviewer:SCHEDULER)
> linux-kernel@vger.kernel.org (open list:SCHEDULER)
>
>
> ?
>
> Leaving the report untrimmed for Peter.
>
> > 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.
> >
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [syzbot] [mm?] WARNING in update_rq_clock (2)
2026-07-03 0:38 [syzbot] [kernel?] WARNING in update_rq_clock (2) syzbot
2026-07-03 9:39 ` Thomas Gleixner
@ 2026-08-03 6:40 ` syzbot
1 sibling, 0 replies; 5+ messages in thread
From: syzbot @ 2026-08-03 6:40 UTC (permalink / raw)
To: bp, dave.hansen, hpa, linux-kernel, linux-mm, luto, mingo, nogikh,
peterz, syzkaller-bugs, tglx, x86
syzbot has found a reproducer for the following issue on:
HEAD commit: cc2b5f627e8c Add linux-next specific files for 20260714
git tree: linux-next
console+strace: https://syzkaller.appspot.com/x/log.txt?x=17122649580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2290ccbf984c524f
dashboard link: https://syzkaller.appspot.com/bug?extid=681e729b2cf0d4860042
compiler: Debian clang version 22.1.8 (++20260613092233+e80beda6e255-1~exp1~20260613092250.77), Debian LLD 22.1.8
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=11908cc6580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1042ec9e580000
Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/6836f8efb1da/disk-cc2b5f62.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/0109d3477cc7/vmlinux-cc2b5f62.xz
kernel image: https://storage.googleapis.com/syzbot-assets/c2e49e350bbf/bzImage-cc2b5f62.xz
IMPORTANT: if you fix the issue, please add the following tag to the commit:
Reported-by: syzbot+681e729b2cf0d4860042@syzkaller.appspotmail.com
------------[ cut here ]------------
debug_locks && !(lock_is_held(&(__rq_lockp(rq))->dep_map) != 0)
WARNING: kernel/sched/sched.h:1652 at lockdep_assert_rq_held kernel/sched/sched.h:1652 [inline], CPU#0: syz-executor108/5647
WARNING: kernel/sched/sched.h:1652 at update_rq_clock+0x34d/0x560 kernel/sched/core.c:865, CPU#0: syz-executor108/5647
Modules linked in:
CPU: 0 UID: 0 PID: 5647 Comm: syz-executor108 Not tainted syzkaller #0 PREEMPT_{RT,(full)}
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 07/24/2026
RIP: 0010:lockdep_assert_rq_held kernel/sched/sched.h:1652 [inline]
RIP: 0010:update_rq_clock+0x34d/0x560 kernel/sched/core.c:865
Code: 48 c1 e8 03 80 3c 28 00 74 08 48 89 df e8 8b f0 9d 00 4c 01 3b 48 83 c4 10 5b 41 5c 41 5d 41 5e 41 5f 5d e9 85 e6 bf 09 cc 90 <0f> 0b 90 e9 42 fd ff ff 48 89 df 48 83 c4 10 5b 41 5c 41 5d 41 5e
RSP: 0018:ffffc90004e9f618 EFLAGS: 00010046
RAX: 0000000000000000 RBX: ffff8880b873b880 RCX: 0000000000000002
RDX: 0000000000000000 RSI: ffffffff8dbfaa0e RDI: ffffffff8bcbd080
RBP: dffffc0000000000 R08: ffffffff8fd0c47f R09: 1ffffffff1fa188f
R10: dffffc0000000000 R11: ffffffff819e4d80 R12: 0000000000000001
R13: dffffc0000000001 R14: ffff8880b873c748 R15: ffff8880b873b880
FS: 00007fb5334a16c0(0000) GS:ffff8881259f2000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007fb5334a0ff8 CR3: 0000000034948000 CR4: 00000000003526f0
Call Trace:
<TASK>
pick_next_task kernel/sched/core.c:6335 [inline]
__schedule+0x3774/0x5530 kernel/sched/core.c:7146
preempt_schedule_irq+0x4d/0xa0 kernel/sched/core.c:7553
irqentry_exit_to_kernel_mode include/linux/irq-entry-common.h:539 [inline]
irqentry_exit+0x14f/0x8f0 kernel/entry/common.c:167
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:674
RIP: 0010:__outb arch/x86/include/asm/shared/io.h:22 [inline]
RIP: 0010:rtc_cmos_write+0x13/0x20 arch/x86/kernel/rtc.c:97
Code: 0f 1f 80 00 00 00 00 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 90 f3 0f 1e fa 55 53 89 f3 89 fd e8 51 9f 59 00 89 d8 e6 70 <89> e8 e6 71 5b 5d c3 cc cc cc cc cc 90 90 90 90 90 90 90 90 90 90
RSP: 0018:ffffc90004e9f970 EFLAGS: 00000293
RAX: 000000000000000f RBX: 000000000000000f RCX: ffff8880350e3e80
RDX: 0000000000000000 RSI: 0000000000000000 RDI: 0000000000000000
RBP: 0000000000000000 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff8e3c3880 R12: ffffffff8dc427d8
R13: dffffc0000000000 R14: dffffc0000000000 R15: ffff8880b8723f90
smpboot_restore_warm_reset_vector arch/x86/kernel/smpboot.c:162 [inline]
arch_cpuhp_cleanup_kick_cpu+0xbf/0x150 arch/x86/kernel/smpboot.c:1129
cpuhp_bp_sync_alive kernel/cpu.c:449 [inline]
cpuhp_bringup_ap+0x90/0x360 kernel/cpu.c:843
cpuhp_invoke_callback+0x434/0x810 kernel/cpu.c:194
__cpuhp_invoke_callback_range kernel/cpu.c:972 [inline]
cpuhp_invoke_callback_range kernel/cpu.c:996 [inline]
cpuhp_up_callbacks kernel/cpu.c:1027 [inline]
_cpu_up+0x2ce/0x5b0 kernel/cpu.c:1674
cpu_up+0x1d2/0x220 kernel/cpu.c:1706
cpu_subsys_online+0x67/0x280 drivers/base/cpu.c:61
device_online+0x181/0x1e0 drivers/base/core.c:4308
online_store+0xd7/0x1a0 drivers/base/core.c:2879
kernfs_fop_write_iter+0x3a5/0x540 fs/kernfs/file.c:345
new_sync_write fs/read_write.c:595 [inline]
vfs_write+0x61e/0xbb0 fs/read_write.c:687
ksys_write+0x156/0x270 fs/read_write.c:739
do_syscall_x64 arch/x86/entry/syscall_64.c:61 [inline]
do_syscall_64+0x17b/0x530 arch/x86/entry/syscall_64.c:85
entry_SYSCALL_64_after_hwframe+0x77/0x7f
RIP: 0033:0x7fb5334ea0a9
Code: c0 79 93 eb d5 48 8d 7c 1d 00 eb 99 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 d0 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007fb5334a11d8 EFLAGS: 00000246 ORIG_RAX: 0000000000000001
RAX: ffffffffffffffda RBX: 00007fb53359ab58 RCX: 00007fb5334ea0a9
RDX: 0000000000000001 RSI: 0000200000000180 RDI: 0000000000000003
RBP: 00007fb53359ab50 R08: 00007fb5334a16c0 R09: 35203a6b63617473
R10: 0000000000000000 R11: 0000000000000246 R12: 00007fb53356c378
R13: 0000200000000100 R14: 0000200000000140 R15: 0000200000000180
</TASK>
----------------
Code disassembly (best guess):
0: 0f 1f 80 00 00 00 00 nopl 0x0(%rax)
7: 90 nop
8: 90 nop
9: 90 nop
a: 90 nop
b: 90 nop
c: 90 nop
d: 90 nop
e: 90 nop
f: 90 nop
10: 90 nop
11: 90 nop
12: 90 nop
13: 90 nop
14: 90 nop
15: 90 nop
16: 90 nop
17: f3 0f 1e fa endbr64
1b: 55 push %rbp
1c: 53 push %rbx
1d: 89 f3 mov %esi,%ebx
1f: 89 fd mov %edi,%ebp
21: e8 51 9f 59 00 call 0x599f77
26: 89 d8 mov %ebx,%eax
28: e6 70 out %al,$0x70
* 2a: 89 e8 mov %ebp,%eax <-- trapping instruction
2c: e6 71 out %al,$0x71
2e: 5b pop %rbx
2f: 5d pop %rbp
30: c3 ret
31: cc int3
32: cc int3
33: cc int3
34: cc int3
35: cc int3
36: 90 nop
37: 90 nop
38: 90 nop
39: 90 nop
3a: 90 nop
3b: 90 nop
3c: 90 nop
3d: 90 nop
3e: 90 nop
3f: 90 nop
---
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.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-08-03 6:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-03 0:38 [syzbot] [kernel?] WARNING in update_rq_clock (2) syzbot
2026-07-03 9:39 ` Thomas Gleixner
2026-07-03 9:48 ` Peter Zijlstra
2026-07-03 10:08 ` Aleksandr Nogikh
2026-08-03 6:40 ` [syzbot] [mm?] " syzbot
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox