From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.13.1
Date: Fri, 30 Jul 2021 16:18:37 +0200 [thread overview]
Message-ID: <20210730141837.30571-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.12.1 have been released. This is a bugfix release.
Changelog:
* build: fix build on musl libc due to missing definition of NAME_MAX
* check:
* batch more work into one transaction when clearing v1 free space inodes
* detect directoris with wrong number of links
* libbtrfsutil: fix race between subvolume iterator and deletion
* mkfs: be more specific about supported profiles for zoned device
* other:
* 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
Shortlog:
David Sterba (5):
btrfs-progs: add nparity for raid1c34 definitions
btrfs-progs: ci: add script to do build test on musl
btrfs-progs: mkfs: update message when creating zoned fs with non-single profiles
btrfs-progs: update CHANGES for 5.13.1
Btrfs progs v5.13.1
Omar Sandoval (1):
libbtrfsutil: fix race between subvolume iterator and deletion
Qu Wenruo (4):
btrfs-progs: docs: fix the out-of-date comment about free space tree support
btrfs-progs: check: batch v1 space cache inodes when clearing
btrfs-progs: check/original: detect directory inode with nlinks >= 2
btrfs-progs: tests: check nlinks for directories
Sidong Yang (1):
btrfs-progs: cmds: fix build on musl when using NAME_MAX
er888kh (1):
libbtrfsutil: fix typo in README example
next reply other threads:[~2021-07-30 14:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 14:18 David Sterba [this message]
2021-07-30 16:17 ` Btrfs progs release 5.13.1 Neal Gompa
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=20210730141837.30571-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;
as well as URLs for NNTP newsgroup(s).