From: syzbot <syzbot+c3a3a153f0190dca5be9@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, fdmanana@suse.com,
josef@toxicpanda.com, linux-btrfs@vger.kernel.org,
linux-kernel@vger.kernel.org, syzkaller-bugs@googlegroups.com,
wqu@suse.com
Subject: Re: [syzbot] [btrfs?] KASAN: slab-use-after-free Read in add_delayed_ref
Date: Mon, 14 Oct 2024 10:34:03 -0700 [thread overview]
Message-ID: <670d560b.050a0220.4cbc0.004e.GAE@google.com> (raw)
In-Reply-To: <670d3f2c.050a0220.3e960.0066.GAE@google.com>
syzbot has bisected this issue to:
commit a3aad8f4f5d9d9a977ee5be32b07bcc083cc8d28
Author: Filipe Manana <fdmanana@suse.com>
Date: Tue Sep 24 16:12:32 2024 +0000
btrfs: qgroups: remove bytenr field from struct btrfs_qgroup_extent_record
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14596887980000
start commit: d61a00525464 Add linux-next specific files for 20241011
git tree: linux-next
final oops: https://syzkaller.appspot.com/x/report.txt?x=16596887980000
console output: https://syzkaller.appspot.com/x/log.txt?x=12596887980000
kernel config: https://syzkaller.appspot.com/x/.config?x=8554528c7f4bf3fb
dashboard link: https://syzkaller.appspot.com/bug?extid=c3a3a153f0190dca5be9
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1266c727980000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=17ce9440580000
Reported-by: syzbot+c3a3a153f0190dca5be9@syzkaller.appspotmail.com
Fixes: a3aad8f4f5d9 ("btrfs: qgroups: remove bytenr field from struct btrfs_qgroup_extent_record")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2024-10-14 17:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 15:56 [syzbot] [btrfs?] KASAN: slab-use-after-free Read in add_delayed_ref syzbot
2024-10-14 17:34 ` syzbot [this message]
2024-10-15 9:55 ` Edward Adam Davis
2024-10-15 10:15 ` [syzbot] " syzbot
2024-10-15 10:49 ` Edward Adam Davis
2024-10-15 11:14 ` [syzbot] " syzbot
2024-10-15 12:26 ` [PATCH next] btrfs: Accessing head_ref within delayed_refs lock Edward Adam Davis
2024-10-15 12:49 ` Filipe Manana
2024-10-15 16:38 ` David Sterba
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=670d560b.050a0220.4cbc0.004e.GAE@google.com \
--to=syzbot+c3a3a153f0190dca5be9@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=fdmanana@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=syzkaller-bugs@googlegroups.com \
--cc=wqu@suse.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.