From: syzbot <syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [f2fs-dev] [syzbot] [f2fs?] kernel BUG in clear_inode (4)
Date: Tue, 09 Sep 2025 17:08:02 -0700 [thread overview]
Message-ID: <68c0c162.050a0220.3c6139.0016.GAE@google.com> (raw)
In-Reply-To: <68c09802.050a0220.3c6139.000e.GAE@google.com>
syzbot has bisected this issue to:
commit c240c87bcd44a1a2375fc8ef8c645d1f1fe76466
Author: Chao Yu <chao@kernel.org>
Date: Tue May 21 06:23:18 2024 +0000
f2fs: fix to do sanity check on blocks for inline_data inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17754b12580000
start commit: f777d1112ee5 Merge tag 'vfs-6.17-rc6.fixes' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f54b12580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f54b12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=429771c55b615e85
dashboard link: https://syzkaller.appspot.com/bug?extid=90266696fe5daacebd35
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a43562580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164dad62580000
Reported-by: syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com
Fixes: c240c87bcd44 ("f2fs: fix to do sanity check on blocks for inline_data inode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
WARNING: multiple messages have this Message-ID (diff)
From: syzbot <syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com>
To: chao@kernel.org, jaegeuk@kernel.org,
linux-f2fs-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [f2fs?] kernel BUG in clear_inode (4)
Date: Tue, 09 Sep 2025 17:08:02 -0700 [thread overview]
Message-ID: <68c0c162.050a0220.3c6139.0016.GAE@google.com> (raw)
In-Reply-To: <68c09802.050a0220.3c6139.000e.GAE@google.com>
syzbot has bisected this issue to:
commit c240c87bcd44a1a2375fc8ef8c645d1f1fe76466
Author: Chao Yu <chao@kernel.org>
Date: Tue May 21 06:23:18 2024 +0000
f2fs: fix to do sanity check on blocks for inline_data inode
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17754b12580000
start commit: f777d1112ee5 Merge tag 'vfs-6.17-rc6.fixes' of git://git.k..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=14f54b12580000
console output: https://syzkaller.appspot.com/x/log.txt?x=10f54b12580000
kernel config: https://syzkaller.appspot.com/x/.config?x=429771c55b615e85
dashboard link: https://syzkaller.appspot.com/bug?extid=90266696fe5daacebd35
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=15a43562580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=164dad62580000
Reported-by: syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com
Fixes: c240c87bcd44 ("f2fs: fix to do sanity check on blocks for inline_data inode")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2025-09-10 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 21:11 [f2fs-dev] [syzbot] [f2fs?] kernel BUG in clear_inode (4) syzbot
2025-09-09 21:11 ` syzbot
2025-09-10 0:08 ` syzbot [this message]
2025-09-10 0:08 ` syzbot
2025-09-10 7:58 ` [f2fs-dev] " Chao Yu via Linux-f2fs-devel
2025-09-10 7:58 ` Chao Yu
2025-09-10 8:25 ` [f2fs-dev] " syzbot
2025-09-10 8:25 ` syzbot
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=68c0c162.050a0220.3c6139.0016.GAE@google.com \
--to=syzbot+90266696fe5daacebd35@syzkaller.appspotmail.com \
--cc=chao@kernel.org \
--cc=jaegeuk@kernel.org \
--cc=linux-f2fs-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.