From: syzbot <syzbot+09bec78ee77613a3efdd@syzkaller.appspotmail.com>
To: adilger.kernel@dilger.ca, boris@bur.io, dsterba@suse.com,
dsterba@suse.cz, fdmanana@suse.com, jack@suse.cz,
libaokun@linux.alibaba.com, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, ojaswin@linux.ibm.com,
ritesh.list@gmail.com, syzkaller-bugs@googlegroups.com,
tytso@mit.edu, wqu@suse.com, yi.zhang@huawei.com
Subject: Re: [syzbot] [ext4?] KASAN: slab-use-after-free Write in do_split
Date: Mon, 28 Sep 2026 17:32:02 -0700 [thread overview]
Message-ID: <6abb0702.80e1c6cc.1e8e5f.0075.GAE@google.com> (raw)
In-Reply-To: <6abae226.69bd487b.a6f8c.000a.GAE@google.com>
syzbot has bisected this issue to:
commit 3f757b56f1c4579fe32b810bce1d39f202964412
Author: Filipe Manana <fdmanana@suse.com>
Date: Fri May 16 16:07:40 2025 +0000
btrfs: unfold transaction aborts at btrfs_create_new_inode()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=16bbf315580000
start commit: 72d3fcf802c4 Linux 7.3-rc5
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=15bbf315580000
console output: https://syzkaller.appspot.com/x/log.txt?x=11bbf315580000
kernel config: https://syzkaller.appspot.com/x/.config?x=718e346eb0b8f38
dashboard link: https://syzkaller.appspot.com/bug?extid=09bec78ee77613a3efdd
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=12379605580000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=127f6325580000
Reported-by: syzbot+09bec78ee77613a3efdd@syzkaller.appspotmail.com
Fixes: 3f757b56f1c4 ("btrfs: unfold transaction aborts at btrfs_create_new_inode()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2026-09-29 0:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-28 21:54 [syzbot] [ext4?] KASAN: slab-use-after-free Write in do_split syzbot
2026-09-29 0:32 ` syzbot [this message]
2026-09-29 1:00 ` Qu Wenruo
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=6abb0702.80e1c6cc.1e8e5f.0075.GAE@google.com \
--to=syzbot+09bec78ee77613a3efdd@syzkaller.appspotmail.com \
--cc=adilger.kernel@dilger.ca \
--cc=boris@bur.io \
--cc=dsterba@suse.com \
--cc=dsterba@suse.cz \
--cc=fdmanana@suse.com \
--cc=jack@suse.cz \
--cc=libaokun@linux.alibaba.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ojaswin@linux.ibm.com \
--cc=ritesh.list@gmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tytso@mit.edu \
--cc=wqu@suse.com \
--cc=yi.zhang@huawei.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.