From: syzbot <syzbot+e0b615318f8fcfc01ceb@syzkaller.appspotmail.com>
To: clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
linux-btrfs@vger.kernel.org, linux-fsdevel@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 btrfs_qgroup_account_extent
Date: Sun, 05 Nov 2023 01:40:03 -0700 [thread overview]
Message-ID: <0000000000001222c4060963af3a@google.com> (raw)
In-Reply-To: <000000000000a6429e0609331930@google.com>
syzbot has bisected this issue to:
commit dce28769a33a95425b007f00842d6e12ffa28f83
Author: Qu Wenruo <wqu@suse.com>
Date: Sat Sep 2 00:13:57 2023 +0000
btrfs: qgroup: use qgroup_iterator_nested to in qgroup_update_refcnt()
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=14f01717680000
start commit: 90b0c2b2edd1 Merge tag 'pinctrl-v6.7-1' of git://git.kerne..
git tree: upstream
final oops: https://syzkaller.appspot.com/x/report.txt?x=16f01717680000
console output: https://syzkaller.appspot.com/x/log.txt?x=12f01717680000
kernel config: https://syzkaller.appspot.com/x/.config?x=4cc8c922092464e7
dashboard link: https://syzkaller.appspot.com/bug?extid=e0b615318f8fcfc01ceb
syz repro: https://syzkaller.appspot.com/x/repro.syz?x=14cae708e80000
C reproducer: https://syzkaller.appspot.com/x/repro.c?x=1354647b680000
Reported-by: syzbot+e0b615318f8fcfc01ceb@syzkaller.appspotmail.com
Fixes: dce28769a33a ("btrfs: qgroup: use qgroup_iterator_nested to in qgroup_update_refcnt()")
For information about bisection process see: https://goo.gl/tpsmEJ#bisection
next prev parent reply other threads:[~2023-11-05 8:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-02 22:42 [syzbot] [btrfs?] KASAN: slab-use-after-free Read in btrfs_qgroup_account_extent syzbot
2023-11-03 3:03 ` syzbot
2023-11-04 20:44 ` syzbot
2023-11-05 8:40 ` syzbot [this message]
2023-11-05 16:00 ` Filipe Manana
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=0000000000001222c4060963af3a@google.com \
--to=syzbot+e0b615318f8fcfc01ceb@syzkaller.appspotmail.com \
--cc=clm@fb.com \
--cc=dsterba@suse.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-fsdevel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox