From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: David Sterba <dsterba@suse.cz>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: [PULL REQUEST v2] btrfs-progs updates, the main part
Date: Tue, 16 Apr 2019 10:23:59 +0800 [thread overview]
Message-ID: <cb2ed110-4ad0-6f72-2dcb-fe150bab461e@gmx.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2734 bytes --]
Hi David,
Here is my pull request for the btrfs-progs:
https://github.com/adam900710/btrfs-progs/tree/for_devel
The basis is the following commit from your devel branch:
commit cfa470d5a6b6b305fed4898b64db31c125b4dcbc (david/devel)
Author: Nikolay Borisov <nborisov@suse.com>
Date: Mon Mar 11 12:20:56 2019 +0200
btrfs-progs: Remove get_argv0_buf
The commit on the top is going to revert 7a12d8470e5f ("btrfs-progs: Do
metadata preallocation as long as we're not modifying extent tree").
You can drop that commit if you have discarded that commit.
The branch passes all selftests, except:
- misc/035
Known bug as the fix is reverted.
- fuzz/003
- fuzz/009
Not a regression, as stable tags also triggers them.
BUG_ON() in commit_transaction get triggered due to ENOSPC.
These two bugs will be addressed soon. but not in this pull.
This pull request include the following features:
Core change:
- check --repair
* Flush/FUA support to avoid breaking metadata CoW
Now btrfs-progs crashing or transaction aborted won't cause
new transid error.
Fixes and Enhancement:
- generic
* Try best copy when reading tree blocks.
* Skip unnecessary retry when one tree block copy fails.
* Avoid back tree block to populate tree block cache.
* Don't BUG_ON() when failed to flush/write super blocks
- check
* File extents repair no longer relies data in extent tree.
* New ability to check and repair free space cache invalid inode mode.
* Update backup roots when commit transaction.
- Misc
* fs_info <-> root parameters cleanup for btrfs_check_leaf/node()
For reference, the devel branch itself contains the following features.
Core change:
- device scan:
* Add the ability to forget a device
Fixes and Enhancement:
- generic:
* Better unrecognized/invalid option handling.
Including btrfs-prop, btrfs-qgroup, btrfs-find-root.
- mkfs:
* Enlarge metadata chunk size to follow kernel size.
- dev-replace:
* Better error handling and error message.
- receive:
* New quite mode.
- dump-tree:
* allow multiple --block to be specified.
- misc
* Fix compiler false alerts about uninitialized variable.
* Update gitignore file to ignore dot files.
* kernel version parsing fix.
Changelog:
v2:
- Reorder the tags to follow the general guideline
- Rebase to latest devel branch
- Add SoB line for commits not authored by me
- Add revert commit other than dropping the offending commit
This should makes merge itself easier.
- Updated the cover letter feature list
Split into two parts, the features introduced in this pull, and
the feature introduced by devel branch.
Thanks,
Qu
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2019-04-16 2:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-16 2:23 Qu Wenruo [this message]
2019-04-18 18:03 ` [PULL REQUEST v2] btrfs-progs updates, the main part David Sterba
2019-04-26 16:14 ` David Sterba
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=cb2ed110-4ad0-6f72-2dcb-fe150bab461e@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=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 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).