From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 3/7] btrfs-progs: Remove recover_get_good_super
Date: Tue, 5 Dec 2017 17:10:06 +0800 [thread overview]
Message-ID: <c57814ce-2b69-50d7-7fb8-63827a7019ef@gmx.com> (raw)
In-Reply-To: <1512463189-24724-4-git-send-email-nborisov@suse.com>
[-- Attachment #1.1: Type: text/plain, Size: 1572 bytes --]
On 2017年12月05日 16:39, Nikolay Borisov wrote:
> Currently getting the good super really consists of just getting the first entry
> on the linked list, since it's the one with the highest transid. So remove
> the function and just use list_first_entry directly.
>
> Signed-off-by: Nikolay Borisov <nborisov@suse.com>
Reviewed-by: Qu Wenruo <wqu@suse.com>
Thanks,
Qu
> ---
> super-recover.c | 13 +++----------
> 1 file changed, 3 insertions(+), 10 deletions(-)
>
> diff --git a/super-recover.c b/super-recover.c
> index 6a13d81b0b29..e12513100f17 100644
> --- a/super-recover.c
> +++ b/super-recover.c
> @@ -177,15 +177,6 @@ static int read_fs_supers(struct btrfs_recover_superblock *recover)
> return 0;
> }
>
> -static struct super_block_record *recover_get_good_super(
> - struct btrfs_recover_superblock *recover)
> -{
> - struct super_block_record *record;
> - record = list_entry(recover->good_supers.next,
> - struct super_block_record, list);
> - return record;
> -}
> -
> static void print_super_info(struct super_block_record *record)
> {
> printf("\t\tdevice name = %s\n", record->device_name);
> @@ -280,7 +271,9 @@ int btrfs_recover_superblocks(const char *dname,
> goto no_recover;
> }
> }
> - record = recover_get_good_super(&recover);
> + record = list_first_entry(&recover.good_supers,
> + struct super_block_record, list);
> +
> root = open_ctree(record->device_name, record->bytenr,
> OPEN_CTREE_RECOVER_SUPER | OPEN_CTREE_WRITES);
> if (!root) {
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 520 bytes --]
next prev parent reply other threads:[~2017-12-05 9:10 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 [this message]
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 ` [PATCH 0/7] Misc btrfs-progs cleanups/fixes Nikolay Borisov
2018-01-23 15:40 ` 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=c57814ce-2b69-50d7-7fb8-63827a7019ef@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=nborisov@suse.com \
/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).