From: David Sterba <dsterba@suse.cz>
To: linux-btrfs@vger.kernel.org
Subject: Btrfs progs pre-release 4.20-rc1
Date: Tue, 15 Jan 2019 14:40:52 +0100 [thread overview]
Message-ID: <20190115134052.GH2900@suse.cz> (raw)
Hi,
this is a pre-release of btrfs-progs, 4.20-rc1.
The 4.20 release is scheduled to this Friday, +3 days (2019-01-18).
Changelog:
* image: fix blockgroups when restroring from multi-device image
* new feature: metadata uuid
* lightweight change of UUID without rewriting all metadata
(incompatible change)
* done by btrfstune -m/-M
* needs kernel support, 5.0+
* check
* more device extent checks and fixes
* can repair dir item with mismatched hash
* mkfs: uuid tree created with proper contents
* other:
* new tests
* libbtrfsutil: fix tests if kernel lacks support for new subvolume ioctls
* build fixes
* doc fixes
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 Disseldorp (1):
btrfs-progs: docs: fix balance -f grammar
David Sterba (5):
btrfs-progs: docs: enhance subvol show documentation and help
btrfs-progs: tests: speed up fsck/037 free space tree test
btrfs-progs: docs: add bootlaoder support section to section 5
Johannes Thumshirn (1):
btrfs-progs: provide etags make target
Nikolay Borisov (6):
btrfs-progs: Add support for metadata_uuid field
btrfs-progs: btrfstune: Add support for changing the user uuid
btrfs-progs: Remove fsid/metdata_uuid fields from fs_info
btrfs-progs: Remove btrfs_fs_info::new_fsid
btrfs-progs: Directly pass root to change_devices_uuid
btrfs-progs: tests: Add tests for changing fsid feature
Omar Sandoval (1):
libbtrfsutil: fix unprivileged tests if kernel lacks support
Qu Wenruo (31):
btrfs-progs: fsck-tests: Move reloc tree images to 020-extent-ref-cases
btrfs-progs: image: Refactor fixup_devices() to fixup_chunks_and_devices()
btrfs-progs: image: Fix block group item flags when restoring multi-device image to single device
btrfs-progs: volumes: Refactor btrfs_alloc_dev_extent() into two functions
btrfs-progs: image: Remove all existing dev extents for later rebuild
btrfs-progs: misc-tests/021: Do extra btrfs check before mounting
btrfs-progs: Makefile.extrawarn: Import cc-disable-warning
btrfs-progs: Makefile.extrawarn: Don't warn on sign compare
btrfs-progs: Fix -Wimplicit-fallthrough warning
btrfs-progs: Fix -Wsuggest-attribute=format warning
btrfs-progs: Fix -Wtype-limits warning
btrfs-progs: Move btrfs_check_nodesize to fsfeatures.c to fix missing-prototypes warning
btrfs-progs: Introduce rescue.h to resolve missing-prototypes for chunk and super rescue
btrfs-progs: Add utils.h include to solve missing-prototypes warning
btrfs-progs: free-space-tree: Remove unused function
btrfs-progs: Fix Wempty-body warning
btrfs-progs: image: Use correct device size when restoring
btrfs-progs: check: lowmem: Add check for overlapping dev extents
btrfs-progs: check: orig: Add ability to detect bad dev extents
btrfs-progs: check: lowmem: Add dev_item check for used bytes and total bytes
btrfs-progs: check: orig: Add dev_item check for used bytes and total bytes
btrfs-progs: tests: Add test image for dev extents beyond device boundary
btrfs-progs: check: lowmem: Add ability to repair dir item with mismatched hash
btrfs-progs: check: orig: Use mismatch_dir_hash_record to record bad dir items
btrfs-progs: check: orig: Add ability to repair dir item with invalid hash
btrfs-progs: tests: check: Make 026-bad-dir-item-name verify if btrfs-check can also repair
btrfs-progs: Export btrfs_create_tree() and move it to disk-io.c
btrfs-progs: mkfs: Create data reloc tree from scratch
btrfs-progs: uuid: Port kernel btrfs_uuid_tree_lookup()
btrfs-progs: uuid: Port btrfs_uuid_tree_add() function
btrfs-progs: Create uuid tree with proper contents
Su Yanjun (1):
btrfs-progs: silence build warning caused by gcc 8 '-Wformat-truncation'
Su Yue (1):
btrfs-progs: trivial fix of line break in repair_inode_nbytes_lowmem()
reply other threads:[~2019-01-15 13:41 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=20190115134052.GH2900@suse.cz \
--to=dsterba@suse.cz \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.