From: Thomas Gleixner <tglx@linutronix.de>
To: Jens Axboe <axboe@kernel.dk>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
syzbot <syzbot+034246a838a10d181e78@syzkaller.appspotmail.com>,
andrealmeid@igalia.com, dave@stgolabs.net, dvhart@infradead.org,
linux-kernel@vger.kernel.org, mingo@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [kernel?] general protection fault in try_to_wake_up (3)
Date: Tue, 09 Sep 2025 22:43:03 +0200 [thread overview]
Message-ID: <875xdruzl4.ffs@tglx> (raw)
In-Reply-To: <4918e983-9964-46a2-aee0-59c91a9c6b35@kernel.dk>
On Tue, Sep 09 2025 at 13:27, Jens Axboe wrote:
> On 9/4/25 10:28 AM, Sebastian Andrzej Siewior wrote:
> Was on the road, and now back at least for a day or two... So I took a
> gander at this one too. One thing that puzzles me is the io_uring traces
> in that syzbot log - if they are to be trusted, it only ever submits an
> io_uring RECVMSG request? IOW, no futex usage on the io_uring side at
> all?
>
> Going to try and download the disk image and kernel and see if I can
> actually run this locally.
It has nothing to do with IO/URING. It reproduces cleanly with the
provided repro.syz. It just takes ages. The bisect log, which contains
the IO/URING muck is irrelevant.
Thanks,
tglx
next prev parent reply other threads:[~2025-09-09 20:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 20:54 [syzbot] [kernel?] general protection fault in try_to_wake_up (3) syzbot
2025-09-02 21:46 ` Peter Zijlstra
2025-09-03 13:07 ` Sebastian Andrzej Siewior
2025-09-03 18:51 ` Jens Axboe
2025-09-04 16:28 ` Sebastian Andrzej Siewior
2025-09-09 18:56 ` Thomas Gleixner
2025-09-09 19:27 ` Jens Axboe
2025-09-09 20:43 ` Thomas Gleixner [this message]
2025-09-09 20:46 ` Jens Axboe
2025-09-10 10:42 ` [PATCH] futex: Prevent use-after-free during requeue-PI Sebastian Andrzej Siewior
2025-09-10 10:48 ` Sebastian Andrzej Siewior
2025-09-20 15:43 ` [tip: locking/urgent] " tip-bot2 for Sebastian Andrzej Siewior
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=875xdruzl4.ffs@tglx \
--to=tglx@linutronix.de \
--cc=andrealmeid@igalia.com \
--cc=axboe@kernel.dk \
--cc=bigeasy@linutronix.de \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=syzbot+034246a838a10d181e78@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/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