From: syzbot <syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com>
To: brauner@kernel.org, chao@kernel.org, djwong@kernel.org,
eadavis@qq.com, hsiangkao@linux.alibaba.com,
linux-erofs@lists.ozlabs.org, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-xfs@vger.kernel.org,
syzkaller-bugs@googlegroups.com, xiang@kernel.org
Subject: Re: [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5)
Date: Sat, 14 Jun 2025 02:46:02 -0700 [thread overview]
Message-ID: <684d44da.050a0220.be214.02b2.GAE@google.com> (raw)
In-Reply-To: <684cb499.a00a0220.c6bd7.0010.GAE@google.com>
syzbot has bisected this issue to:
commit 1d191b4ca51d73699cb127386b95ac152af2b930
Author: Gao Xiang <hsiangkao@linux.alibaba.com>
Date: Mon Mar 10 09:54:58 2025 +0000
erofs: implement encoded extent metadata
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=1352dd70580000
start commit: 02adc1490e6d Merge tag 'spi-fix-v6.16-rc1' of git://git.ke..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=10d2dd70580000
console output: https://syzkaller.appspot.com/x/log.txt?x=1752dd70580000
kernel config: https://syzkaller.appspot.com/x/.config?x=162faeb2d1eaefb4
dashboard link: https://syzkaller.appspot.com/bug?extid=d8f000c609f05f52d9b5
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=115f9e0c580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1688b10c580000
Reported-by: syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com
Fixes: 1d191b4ca51d ("erofs: implement encoded extent metadata")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-06-14 9:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 23:30 [syzbot] [iomap?] [erofs?] WARNING in iomap_iter (5) syzbot
2025-06-14 9:46 ` syzbot [this message]
2025-06-15 5:05 ` [PATCH] erofs: confirm big pcluster before setting extents Edward Adam Davis
2025-06-15 5:49 ` Gao Xiang
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=684d44da.050a0220.be214.02b2.GAE@google.com \
--to=syzbot+d8f000c609f05f52d9b5@syzkaller.appspotmail.com \
--cc=brauner@kernel.org \
--cc=chao@kernel.org \
--cc=djwong@kernel.org \
--cc=eadavis@qq.com \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=xiang@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