[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6906ee76.050a0220.29fc44.0016.GAE@google.com>
Date: Sat, 01 Nov 2025 22:39:02 -0700
From: syzbot <syzbot+3686758660f980b402dc@...kaller.appspotmail.com>
To: brauner@...nel.org, chao@...nel.org, djwong@...nel.org, jaegeuk@...nel.org,
joannelkoong@...il.com, linux-f2fs-devel@...ts.sourceforge.net,
linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-xfs@...r.kernel.org, syzkaller-bugs@...glegroups.com
Subject: Re: [syzbot] [iomap?] kernel BUG in folio_end_read (2)
syzbot has bisected this issue to:
commit 51311f045375984dabdf8cc523e80d39a4c3dd5a
Author: Joanne Koong <joannelkoong@...il.com>
Date: Fri Sep 26 00:26:02 2025 +0000
iomap: track pending read bytes more optimally
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=103a0012580000
start commit: 98bd8b16ae57 Add linux-next specific files for 20251031
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=123a0012580000
console output: https://syzkaller.appspot.com/x/log.txt?x=143a0012580000
kernel config: https://syzkaller.appspot.com/x/.config?x=63d09725c93bcc1c
dashboard link: https://syzkaller.appspot.com/bug?extid=3686758660f980b402dc
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=176fc342580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=10403f34580000
Reported-by: syzbot+3686758660f980b402dc@...kaller.appspotmail.com
Fixes: 51311f045375 ("iomap: track pending read bytes more optimally")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
Powered by blists - more mailing lists