From: Nikolay Borisov <nborisov@suse.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 0/7] Misc btrfs-progs cleanups/fixes
Date: Mon, 15 Jan 2018 11:17:33 +0200 [thread overview]
Message-ID: <e5d7b12d-d669-0f7d-caf6-2b2b8340f01d@suse.com> (raw)
In-Reply-To: <1512463189-24724-1-git-send-email-nborisov@suse.com>
On 5.12.2017 10:39, Nikolay Borisov wrote:
> Here is a series doing some minor code cleanups, hopefully making the code
> more idiomatic and easier to follow. They should be pretty low-risk and
> introduce no functional changes (patches 1-5).
>
> The the last 2 patches deal with a regression of btrfs rescue super-recovery.
> Turns out this was broken for sometime. Patch 6 introduces a regression test
> which hopefully will prevent further occurences and patch 7 fixes the actual
> bug.
>
> Nikolay Borisov (7):
> btrfs-progs: Explictly state test.sh must be executable
> btrfs-progs: Factor out common print_device_info
> btrfs-progs: Remove recover_get_good_super
> btrfs-progs: Use list_for_each_entry in write_dev_all_supers
> btrfs-progs: Document logic of btrfs_read_dev_super
> btrfs-progs: Add test for super block recovery
> btrfs-progs: Fix super-recovery
>
> chunk-recover.c | 18 -------
> disk-io.c | 21 ++++++--
> super-recover.c | 28 ++---------
> tests/README.md | 4 +-
> tests/fsck-tests/029-superblock-recovery/test.sh | 64 ++++++++++++++++++++++++
> utils.c | 18 +++++++
> utils.h | 3 ++
> 7 files changed, 110 insertions(+), 46 deletions(-)
> create mode 100755 tests/fsck-tests/029-superblock-recovery/test.sh
Gentle ping since I'd like to get this into next btrfs-progs version,
especially the "fix super-recovery" patch.
>
next prev parent reply other threads:[~2018-01-15 9:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 8:39 [PATCH 0/7] Misc btrfs-progs cleanups/fixes Nikolay Borisov
2017-12-05 8:39 ` [PATCH 1/7] btrfs-progs: Explictly state test.sh must be executable Nikolay Borisov
2017-12-05 8:57 ` Qu Wenruo
2017-12-05 8:39 ` [PATCH 2/7] btrfs-progs: Factor out common print_device_info Nikolay Borisov
2017-12-05 9:02 ` Qu Wenruo
2017-12-05 8:39 ` [PATCH 3/7] btrfs-progs: Remove recover_get_good_super Nikolay Borisov
2017-12-05 9:10 ` Qu Wenruo
2017-12-05 8:39 ` [PATCH 4/7] btrfs-progs: Use list_for_each_entry in write_dev_all_supers Nikolay Borisov
2017-12-05 9:14 ` Qu Wenruo
2017-12-05 9:16 ` Nikolay Borisov
2017-12-07 9:10 ` [PATCH v2] btrfs-progs: Replace usage of list_for_each with list_for_each_entry Nikolay Borisov
2017-12-07 9:59 ` Qu Wenruo
2017-12-05 8:39 ` [PATCH 5/7] btrfs-progs: Document logic of btrfs_read_dev_super Nikolay Borisov
2017-12-05 9:21 ` Qu Wenruo
2017-12-05 8:39 ` [PATCH 6/7] btrfs-progs: Add test for super block recovery Nikolay Borisov
2017-12-05 9:33 ` Qu Wenruo
2017-12-05 10:04 ` Nikolay Borisov
2017-12-05 11:12 ` Qu Wenruo
2017-12-05 11:26 ` Nikolay Borisov
2017-12-05 12:13 ` Qu Wenruo
2018-01-23 15:07 ` David Sterba
2018-01-23 15:29 ` Nikolay Borisov
2018-01-23 15:39 ` David Sterba
2017-12-05 8:39 ` [PATCH 7/7] btrfs-progs: Fix super-recovery Nikolay Borisov
2017-12-05 9:35 ` Qu Wenruo
2018-01-15 9:17 ` Nikolay Borisov [this message]
2018-01-23 15:40 ` [PATCH 0/7] Misc btrfs-progs cleanups/fixes 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=e5d7b12d-d669-0f7d-caf6-2b2b8340f01d@suse.com \
--to=nborisov@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).