[fs?] [net?] INFO: rcu detected stall in clock_adjtime (2)

[syzbot]

Hello,

syzbot found the following issue on:

HEAD commit: 1dc3731daf1f Merge tag 'for-6.4-rc1-tag' of git://git.kern..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=13c69b96280000
kernel config: https://syzkaller.appspot.com/x/.config?x=8bc832f563d8bf38
dashboard link: https://syzkaller.appspot.com/bug?extid=f6fc958edb6458a61aa3
compiler: gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU Binutils for Debian) 2.35.2
CC: [linux-...@vger.kernel.org linux-...@vger.kernel.org net...@vger.kernel.org tg...@linutronix.de]

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

Downloadable assets:
disk image: https://storage.googleapis.com/syzbot-assets/c41d6364878c/disk-1dc3731d.raw.xz
vmlinux: https://storage.googleapis.com/syzbot-assets/ed2d9614f1c1/vmlinux-1dc3731d.xz
kernel image: https://storage.googleapis.com/syzbot-assets/903dc319e88d/bzImage-1dc3731d.xz

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

rcu: INFO: rcu_preempt detected expedited stalls on CPUs/tasks: { 1-...D } 2677 jiffies s: 44133 root: 0x2/.
rcu: blocking rcu_node structures (internal RCU debug):
Sending NMI from CPU 0 to CPUs 1:
NMI backtrace for cpu 1
CPU: 1 PID: 16468 Comm: syz-executor.2 Not tainted 6.4.0-rc1-syzkaller-00011-g1dc3731daf1f #0
Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Google 04/14/2023
RIP: 0010:rcu_is_watching+0x0/0xb0 kernel/rcu/tree.c:691
Code: 66 2e 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 48 c7 c7 e0 fb 4d 8a e8 00 dd a1 08 65 8a 05 e5 60 96 7e 0f b6 c0 c3 0f 1f 44 00 00 <f3> 0f 1e fa 55 53 65 ff 05 6b 46 96 7e e8 be dc a1 08 48 c7 c3 e8
RSP: 0018:ffffc900001e0c88 EFLAGS: 00000047
RAX: 0000000000000001 RBX: 1ffff9200003c194 RCX: ffffffff8165efbc
RDX: 0000000000000001 RSI: 0000000000000008 RDI: ffffffff8e7a7150
RBP: 0000000000000001 R08: 0000000000000000 R09: ffffffff8e7a7157
R10: fffffbfff1cf4e2a R11: 0000000000000000 R12: 0000000000000000
R13: 0000000000000000 R14: ffff888021c07300 R15: 0000000000000000
FS: 00007f637713c700(0000) GS:ffff8880b9900000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 00007f637713c718 CR3: 0000000076715000 CR4: 0000000000350ee0
Call Trace:
<IRQ>
trace_lock_acquire include/trace/events/lock.h:24 [inline]
lock_acquire+0x470/0x520 kernel/locking/lockdep.c:5662
__raw_spin_lock include/linux/spinlock_api_smp.h:133 [inline]
_raw_spin_lock+0x2e/0x40 kernel/locking/spinlock.c:154
spin_lock include/linux/spinlock.h:350 [inline]
advance_sched+0xd2/0xd20 net/sched/sch_taprio.c:929
__run_hrtimer kernel/time/hrtimer.c:1685 [inline]
__hrtimer_run_queues+0x5fa/0xbe0 kernel/time/hrtimer.c:1749
hrtimer_interrupt+0x320/0x7b0 kernel/time/hrtimer.c:1811
local_apic_timer_interrupt arch/x86/kernel/apic/apic.c:1095 [inline]
__sysvec_apic_timer_interrupt+0x14a/0x430 arch/x86/kernel/apic/apic.c:1112
sysvec_apic_timer_interrupt+0x92/0xc0 arch/x86/kernel/apic/apic.c:1106
</IRQ>
<TASK>
asm_sysvec_apic_timer_interrupt+0x1a/0x20 arch/x86/include/asm/idtentry.h:645
RIP: 0010:__raw_spin_unlock_irqrestore include/linux/spinlock_api_smp.h:152 [inline]
RIP: 0010:_raw_spin_unlock_irqrestore+0x3c/0x70 kernel/locking/spinlock.c:194
Code: 74 24 10 e8 96 34 53 f7 48 89 ef e8 be a2 53 f7 81 e3 00 02 00 00 75 25 9c 58 f6 c4 02 75 2d 48 85 db 74 01 fb bf 01 00 00 00 <e8> 0f 77 45 f7 65 8b 05 30 09 f1 75 85 c0 74 0a 5b 5d c3 e8 ac 2e
RSP: 0018:ffffc9000f437a98 EFLAGS: 00000206
RAX: 0000000000000002 RBX: 0000000000000200 RCX: 1ffffffff22a50be
RDX: 0000000000000000 RSI: 0000000000000001 RDI: 0000000000000001
RBP: ffff8880b982b840 R08: 0000000000000001 R09: ffffffff91527d07
R10: 0000000000000001 R11: 0000000000000002 R12: 0000000000000004
R13: 0000000000000000 R14: 0000000000000000 R15: dffffc0000000000
clock_was_set+0x610/0x810 kernel/time/hrtimer.c:970
timekeeping_inject_offset+0x4b4/0x620 kernel/time/timekeeping.c:1395
do_adjtimex+0x333/0xa40 kernel/time/timekeeping.c:2444
do_clock_adjtime kernel/time/posix-timers.c:1122 [inline]
__do_sys_clock_adjtime+0x163/0x270 kernel/time/posix-timers.c:1134
do_syscall_x64 arch/x86/entry/common.c:50 [inline]
do_syscall_64+0x39/0xb0 arch/x86/entry/common.c:80
entry_SYSCALL_64_after_hwframe+0x63/0xcd
RIP: 0033:0x7f637648c169
Code: 28 00 00 00 75 05 48 83 c4 28 c3 e8 f1 19 00 00 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 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48
RSP: 002b:00007f637713c168 EFLAGS: 00000246 ORIG_RAX: 0000000000000131
RAX: ffffffffffffffda RBX: 00007f63765ac120 RCX: 00007f637648c169
RDX: 0000000000000000 RSI: 0000000020000040 RDI: 0000000000000000
RBP: 00007f63764e7ca1 R08: 0000000000000000 R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000000
R13: 00007fff54093f9f R14: 00007f637713c300 R15: 0000000000022000
</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 bug is already fixed, let syzbot know by replying with:
#syz fix: exact-commit-title

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

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

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

[syzbot]

Sending this report to the next reporting stage.