From: Steven Rostedt <rostedt@goodmis.org>
To: syzbot <syzbot+2dd9d02f60775ce5c1fb@syzkaller.appspotmail.com>
Cc: linux-kernel@vger.kernel.org, linux-trace-kernel@vger.kernel.org,
mathieu.desnoyers@efficios.com, mhiramat@kernel.org,
syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [trace?] KASAN: use-after-free Write in ring_buffer_read_page
Date: Tue, 2 Jun 2026 12:28:29 -0400 [thread overview]
Message-ID: <20260602122829.4a91864f@gandalf.local.home> (raw)
In-Reply-To: <6a1ede7b.b4221f80.1326c5.0003.GAE@google.com>
On Tue, 02 Jun 2026 06:45:31 -0700
syzbot <syzbot+2dd9d02f60775ce5c1fb@syzkaller.appspotmail.com> wrote:
> syzbot found the following issue on:
>
> HEAD commit: e7ae89a0c97c Linux 7.1-rc5
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=16f06e2e580000
> kernel config: https://syzkaller.appspot.com/x/.config?x=58acee1ac5406016
> dashboard link: https://syzkaller.appspot.com/bug?extid=2dd9d02f60775ce5c1fb
> 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.
Looks like the test was doing something really weird to trigger this.
Without a reproducer, it's pretty much impossible to find out what
happened. Maybe AI could do it?
-- Steve
next prev parent reply other threads:[~2026-06-02 16:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 13:45 syzbot
2026-06-02 16:28 ` Steven Rostedt [this message]
2026-06-03 1:34 ` Masami Hiramatsu
2026-06-03 6:38 ` Aleksandr Nogikh
2026-06-03 8:49 ` Alexander Potapenko
2026-06-08 14:01 ` Yash Suthar
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=20260602122829.4a91864f@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mhiramat@kernel.org \
--cc=syzbot+2dd9d02f60775ce5c1fb@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
all inboxes | Powered by JetHome®