From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <wqu@suse.com>
Cc: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v2 4/4] btrfs: Do super block verification before writing it to disk
Date: Tue, 24 Apr 2018 15:14:31 +0200 [thread overview]
Message-ID: <20180424131431.GE21272@twin.jikos.cz> (raw)
In-Reply-To: <20180424044809.29838-5-wqu@suse.com>
On Tue, Apr 24, 2018 at 12:48:09PM +0800, Qu Wenruo wrote:
> -static int btrfs_validate_super(struct btrfs_fs_info *fs_info)
> +/*
> + * Check the validation of btrfs super block.
> + *
> + * @sb: super block to check
> + * @super_mirror: the super block number to check its bytenr.
> + * 0 means the primary (1st) sb, 1 and 2 means 2nd and
> + * 3rd backup sb, while -1 means to skip bytenr check.
Please format the values like:
/*
* Check the validity of btrfs super block
*
* @sb: super block to check
* @super_mirror: the super block number to check its bytenr:
* 0 means the primary (1st) sb,
* 1 and 2 means 2nd and 3rd backup copy
* -1 means to skip bytenr check
*/
> + */
> +static int btrfs_validate_super(struct btrfs_fs_info *fs_info,
> + struct btrfs_super_block *sb,
> + int super_mirror)
> {
> - struct btrfs_super_block *sb = fs_info->super_copy;
> u64 nodesize = btrfs_super_nodesize(sb);
> u64 sectorsize = btrfs_super_sectorsize(sb);
> int ret = 0;
> @@ -4088,9 +4109,10 @@ static int btrfs_validate_super(struct btrfs_fs_info *fs_info)
> ret = -EINVAL;
> }
>
> - if (btrfs_super_bytenr(sb) != BTRFS_SUPER_INFO_OFFSET) {
> - btrfs_err(fs_info, "super offset mismatch %llu != %u",
> - btrfs_super_bytenr(sb), BTRFS_SUPER_INFO_OFFSET);
> + if (super_mirror >= 0 && btrfs_super_bytenr(sb) !=
> + btrfs_sb_offset(super_mirror)) {
The preferred condition split is after the operators, not in the middle
of the expression. Like this:
if (super_mirror >= 0 &&
btrfs_super_bytenr(sb) != btrfs_sb_offset(super_mirror)) {
next prev parent reply other threads:[~2018-04-24 13:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-24 4:48 [PATCH v2 0/4] btrfs: Add write time super block validation Qu Wenruo
2018-04-24 4:48 ` [PATCH v2 1/4] btrfs: Rename btrfs_check_super_valid() to btrfs_validate_super() Qu Wenruo
2018-04-24 4:48 ` [PATCH v2 2/4] btrfs: Add incompat flags check for btrfs_check_super_valid() Qu Wenruo
2018-04-24 10:48 ` David Sterba
2018-04-24 11:28 ` Qu Wenruo
2018-04-24 11:30 ` David Sterba
2018-04-24 12:03 ` Qu Wenruo
2018-04-24 4:48 ` [PATCH v2 3/4] btrfs: Add csum type " Qu Wenruo
2018-04-24 4:48 ` [PATCH v2 4/4] btrfs: Do super block verification before writing it to disk Qu Wenruo
2018-04-24 13:14 ` David Sterba [this message]
2018-05-10 14:43 ` [PATCH v2 0/4] btrfs: Add write time super block validation David Sterba
2018-05-11 2:57 ` Qu Wenruo
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=20180424131431.GE21272@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=wqu@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