From: Peter Zijlstra <peterz@infradead.org>
To: syzbot <syzbot+93cc6b9a8a81c9e47978@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, luto@kernel.org,
syzkaller-bugs@googlegroups.com, tglx@kernel.org
Subject: Re: [syzbot] [kernel?] WARNING in irqentry_exit (2)
Date: Wed, 5 Aug 2026 08:16:07 +0200 [thread overview]
Message-ID: <20260805061607.GM776954@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <6a728030.9511d2ce.1fc5b9.035f.GAE@google.com>
On Tue, Aug 04, 2026 at 05:13:36PM -0700, syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit: 3708dd948844 Merge tag 'pm-7.2-rc6' of git://git.kernel.or..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=17973632580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=f221a1b5d497ed15
> dashboard link: https://syzkaller.appspot.com/bug?extid=93cc6b9a8a81c9e47978
> 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/244376930b41/disk-3708dd94.raw.xz
> vmlinux: https://storage.googleapis.com/syzbot-assets/6a4fdb2a8dcf/vmlinux-3708dd94.xz
> kernel image: https://storage.googleapis.com/syzbot-assets/6d326f1f8ed8/bzImage-3708dd94.xz
>
> IMPORTANT: if you fix the issue, please add the following tag to the commit:
> Reported-by: syzbot+93cc6b9a8a81c9e47978@syzkaller.appspotmail.com
>
> ------------[ cut here ]------------
> __lockdep_enabled && this_cpu_read(hardirqs_enabled)
> WARNING: ./include/linux/hrtimer_rearm.h:17 at hrtimer_test_and_clear_rearm_deferred_tif include/linux/hrtimer_rearm.h:17 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at hrtimer_rearm_deferred_tif include/linux/hrtimer_rearm.h:52 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at rseq_grant_slice_extension include/linux/rseq_entry.h:236 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at __exit_to_user_mode_loop kernel/entry/common.c:54 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at exit_to_user_mode_loop kernel/entry/common.c:101 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at __exit_to_user_mode_prepare include/linux/irq-entry-common.h:207 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at irqentry_exit_to_user_mode_prepare include/linux/irq-entry-common.h:244 [inline], CPU#0: syz.2.3762/30761
> WARNING: ./include/linux/hrtimer_rearm.h:17 at irqentry_exit_to_user_mode include/linux/irq-entry-common.h:315 [inline], CPU#0: syz.2.3762/30761
I'm thinking this:
https://lore.kernel.org/r/20260803071940.GX49951@noisy.programming.kicks-ass.net
might fix.
prev parent reply other threads:[~2026-08-05 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 0:13 [syzbot] [kernel?] WARNING in irqentry_exit (2) syzbot
2026-08-05 6:16 ` Peter Zijlstra [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260805061607.GM776954@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=syzbot+93cc6b9a8a81c9e47978@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox