From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 7.3
Date: Sat, 24 Oct 2026 00:46:58 +0200 [thread overview]
Message-ID: <20261023224700.103333-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 7.3 have been released (version 7.2 was skipped).
I've received several security reports, fixes will be in a future release. The
codebase is old and if you run AI scanners you will find bugs, probably the
same ones. The security policy and threat model is WIP.
Changelog:
* zoned mode: open host-managed devices with direct io, page cache cannot be
used for synchronization due to ordering
* convert: set creation and change time of the root subvolume
* mkfs:
* set creation and change time of the created subvolumes
* make -O mixed work same as --mixed, so it does not create split block
groups by mistake
* for reproducible builds, honor SOURCE_DATE_EPOCH, SEED and for --rootdir
order the files deterministically
* corrupt-block: allow inode and dir item corruption to use option --value
* check:
* detect file extents for wrong inode types
* on zoned filesystem, detect leaked active zones
* restore: handle inline extents larger than 4KiB, e.g. created on systems with
64KiB pages
* build:
* minimal version of util-linux is 2.31
* scrub limit: set to the original limit only after all devices finish
* other
* new and updated tests
* documentation updates
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/v7.3
Python: https://pypi.org/project/btrfsutil/
reply other threads:[~2026-10-23 22:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261023224700.103333-1-dsterba@suse.com \
--to=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