On Tue, 2 Jun 2026 12:28:29 -0400 Steven Rostedt <[email protected]> wrote:
> On Tue, 02 Jun 2026 06:45:31 -0700 > syzbot <[email protected]> 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? > Does the "I don't have any reproducer for this issue yet." means this is not reproducible even if it runs completely same sequence in the console output? If so, might this be a timing related issue? (e.g. read v.s. write-event) Thanks, -- Masami Hiramatsu (Google) <[email protected]>
