From: David Sterba <dsterba@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs release 5.19.1
Date: Mon, 12 Sep 2022 19:14:24 +0200 [thread overview]
Message-ID: <20220912171425.21222-1-dsterba@suse.com> (raw)
Hi,
btrfs-progs version 5.19.1 have been released. This is a bugfix release.
Changelog:
* fix memory leaks (extent buffer, path)
* check: verify block device size vs item
* rescue fix-device-size: allow to shrink device item
* receive: fix crash on wrong pinter free()
* other:
* experimental: support for block-group-tree
* documentation updates
* new tests
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 (7):
btrfs-progs: docs: add new 5.19 features
btrfs-progs: docs: add stub page for kernel changes
btrfs-progs: tests: add matching line for extent leaks to scan-results
btrfs-progs: mkfs: drop numeric flag from -O and -R option list
btrfs-progs: tests: fix misc/016 encoded write, permissions of send stream file
btrfs-progs: update CHANGES for 5.19.1
Btrfs progs v5.19.1
Qu Wenruo (9):
btrfs-progs: fix eb leak caused by missing btrfs_release_path() call.
btrfs-progs: check: verify the underlying block device size is valid
btrfs-progs: tests: add test case for shrunk device
btrfs-progs: rescue: allow fix-device-size to shrink device item
btrfs-progs: mkfs: dynamically modify mkfs blocks array
btrfs-progs: don't save block group root into super block
btrfs-progs: separate block group tree from extent tree v2
btrfs-progs: btrfstune: add the ability to convert to block group tree feature
btrfs-progs: mkfs: add artificial dependency for block group tree
Su Yue (1):
btrfs-progs: free extent buffer after repairing wrong transid eb
Wang Yugui (1):
btrfs-progs: receive: fix a segfault when passing error pointer to free()
reply other threads:[~2022-09-12 17:20 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=20220912171425.21222-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