mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: syzbot <syzbot+480676efc0c3a76b5214@syzkaller.appspotmail.com>
To: boris@bur.io, clm@fb.com, dsterba@suse.com, josef@toxicpanda.com,
	 linux-btrfs@vger.kernel.org, linux-kernel@vger.kernel.org,
	nogikh@google.com,  quwenruo.btrfs@gmx.com,
	syzkaller-bugs@googlegroups.com, wqu@suse.com
Subject: Re: [syzbot] [btrfs?] WARNING in __btrfs_free_extent (3)
Date: Sat, 01 Aug 2026 21:24:02 -0700	[thread overview]
Message-ID: <6a6ec662.6ce73036.24301b.001b.GAE@google.com> (raw)
In-Reply-To: <000000000000e93ea70620fe777a@google.com>

syzbot suspects this issue was fixed by commit:

commit 1e92637722ae4bd417f7a37e8d1485dc23b93935
Author: Boris Burkov <boris@bur.io>
Date:   Mon May 11 20:07:11 2026 +0000

    btrfs: check for subvolume before deleting squota qgroup

bisection log:  https://syzkaller.appspot.com/x/bisect.txt?x=17e815b9580000
start commit:   f5459048c38a Merge tag 'i2c-for-7.0-final' of git://git.ke..
git tree:       upstream
kernel config:  https://syzkaller.appspot.com/x/.config?x=45cb3c58fd963c27
dashboard link: https://syzkaller.appspot.com/bug?extid=480676efc0c3a76b5214
syz repro:      https://syzkaller.appspot.com/x/repro.syz?x=10c65106580000
C reproducer:   https://syzkaller.appspot.com/x/repro.c?x=15261036580000

If the result looks correct, please mark the issue as fixed by replying with:

#syz fix: btrfs: check for subvolume before deleting squota qgroup

For information about bisection process see: https://goo.gl/tpsmEJ#bisection

      parent reply	other threads:[~2026-08-02  4:24 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 17:59 syzbot
2024-08-31 22:33 ` Qu Wenruo
2024-09-02 10:23   ` Aleksandr Nogikh
2025-12-13 15:21 ` syzbot
2026-08-02  4:24 ` syzbot [this message]

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=6a6ec662.6ce73036.24301b.001b.GAE@google.com \
    --to=syzbot+480676efc0c3a76b5214@syzkaller.appspotmail.com \
    --cc=boris@bur.io \
    --cc=clm@fb.com \
    --cc=dsterba@suse.com \
    --cc=josef@toxicpanda.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nogikh@google.com \
    --cc=quwenruo.btrfs@gmx.com \
    --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
all inboxes | Powered by JetHome®