From: David Sterba <dsterba@suse.cz>
To: Filipe Manana <fdmanana@kernel.org>
Cc: David Sterba <dsterba@suse.com>,
linux-btrfs@vger.kernel.org, Mark Harmstone <maharmstone@fb.com>
Subject: Re: Btrfs progs release 6.16.1
Date: Thu, 18 Sep 2025 02:33:44 +0200 [thread overview]
Message-ID: <20250918003344.GH5333@suse.cz> (raw)
In-Reply-To: <CAL3q7H4vXmz4pGXayq98XZqPbFh6H6Z4=eaM-gFX7fsRLnFfEQ@mail.gmail.com>
On Wed, Sep 17, 2025 at 04:41:43PM +0100, Filipe Manana wrote:
> With this btrfs-progs release, running 'btrfs check' fails on a
> filesystem created by an older mkfs.btrfs.
> A bisection points to:
>
> commit e2cf6a03796b73d446b086022c0dfcf6a6552928
> Author: Mark Harmstone <maharmstone@fb.com>
> Date: Fri Jul 18 15:26:27 2025 +0100
>
> btrfs-progs: use btrfs_lookup_block_group() in check_free_space_tree()
Thanks for the report, I'll do a release with this patch reverted unless
there's an updated fix.
next prev parent reply other threads:[~2025-09-18 0:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 17:50 Btrfs progs release 6.16.1 David Sterba
2025-09-17 15:41 ` Filipe Manana
2025-09-18 0:33 ` David Sterba [this message]
2025-09-18 5:10 ` Mark Harmstone
2025-09-18 12:17 ` Filipe Manana
2025-09-18 13:05 ` Mark Harmstone
2025-09-21 18:25 ` Chris Murphy
2025-09-21 18:32 ` Chris Murphy
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=20250918003344.GH5333@suse.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=fdmanana@kernel.org \
--cc=linux-btrfs@vger.kernel.org \
--cc=maharmstone@fb.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