From: David Sterba <dsterba@suse.cz>
To: David Sterba <dsterba@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 6.9.1 (do not use)
Date: Tue, 25 Jun 2024 17:47:33 +0200 [thread overview]
Message-ID: <20240625154733.GX25756@twin.jikos.cz> (raw)
In-Reply-To: <20240624222951.2807-1-dsterba@suse.com>
There's a report that subvolume names in the 'subvolume list' output are
trimmed (missing last character). This is serious enough to make a fixup
release. ETA tomorrow in case something else pops up.
On Tue, Jun 25, 2024 at 12:29:47AM +0200, David Sterba wrote:
> Hi,
>
> btrfs-progs version 6.9.1 have been released. This is a bugfix release.
>
> Note: raid-stripe-tree has recently got a on-disk format update which is not
> backward compatible, until the patches are in kernel (ETA release 6.11) use v6.9
> or lower, both need either DEBUG or experimental build
>
> Changelog:
>
> * fix detection of intermediate super block flags (e.g. csum change and
> other conversions)
> * raid-stripe-tree support (still experimental):
> * moved under experimental build flags (mkfs, convert)
> * format change, removed encoding type; backward incompatible
> * receive dump: escape special chars in xattr names and values, and clone
> source path
> * tune change csum: fix reservation size when starting a transaction
> * other:
> * new and updated tests
> * updated CI images, new reference build targets
> * cleanups and refactoring
>
> Tarballs: https://www.kernel.org/pub/linux/kernel/people/kdave/btrfs-progs/
> Git: git://git.kernel.org/pub/scm/linux/kernel/git/kdave/btrfs-progs.git
> Release: https://github.com/kdave/btrfs-progs/releases/tag/v6.9.1
prev parent reply other threads:[~2024-06-25 15:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 22:29 Btrfs progs release 6.9.1 David Sterba
2024-06-25 15:47 ` David Sterba [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=20240625154733.GX25756@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=dsterba@suse.com \
--cc=linux-btrfs@vger.kernel.org \
/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