linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: Nikolay Borisov <nborisov@suse.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 7/8] btrfs: verify checksum for all devices in mount context
Date: Wed, 28 Mar 2018 06:48:49 +0800	[thread overview]
Message-ID: <01ec84dd-658e-4d04-a332-71f9513cbc3f@oracle.com> (raw)
In-Reply-To: <63df7a25-7b4b-bb7e-6b85-383c3dcdc54e@suse.com>



On 03/27/2018 08:21 PM, Nikolay Borisov wrote:
> 
> 
> On 26.03.2018 11:27, Anand Jain wrote:
>> During mount context, we aren't verifying the superblock checksum
>> for all the devices, instead, we verify it only for the
>> struct btrfs_fs_device::latest_bdev. This patch fixes it
>> by moving the checksum verification code from the function open_ctree()
>> into the function btrfs_read_dev_one_super().
>>
>> By doing this now we are verifying the superblock checksum
>> in the mount-context, device-replace and, device-delete context.
> 
> Which call chain provides the device-replace and device-delete contexts?
> I think it is worth it documenting them in the changelog.

  Will copy it here from the cover-letter.

>>
>> Signed-off-by: Anand Jain <anand.jain@oracle.com>
> 
> Reviewed-by: Nikolay Borisov <nborisov@suse.com>

> 
>> ---
>>   fs/btrfs/disk-io.c | 35 +++++++++++++++++------------------
>>   1 file changed, 17 insertions(+), 18 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index 6299ab18da5f..3cc50041c0b9 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -2565,24 +2565,6 @@ int open_ctree(struct super_block *sb,
>>   	}
>>   
>>   	/*
>> -	 * We want to check superblock checksum, the type is stored inside.
>> -	 * Pass the whole disk block of size BTRFS_SUPER_INFO_SIZE (4k).
>> -	 */
>> -	err = btrfs_check_super_csum(bh->b_data);
>> -	if (err) {
>> -		if (err == -EINVAL)
>> -			pr_err("BTRFS error (device %pg): "\
>> -				"unsupported checksum algorithm",
>> -				fs_devices->latest_bdev);
>> -		else
>> -			pr_err("BTRFS error (device %pg): "\
>> -				"superblock checksum mismatch",
>> -				fs_devices->latest_bdev);
>> -		brelse(bh);
>> -		goto fail_alloc;
>> -	}
>> -
>> -	/*
>>   	 * super_copy is zeroed at allocation time and we never touch the
>>   	 * following bytes up to INFO_SIZE, the checksum is calculated from
>>   	 * the whole block of INFO_SIZE
>> @@ -3128,6 +3110,7 @@ int btrfs_read_dev_one_super(struct block_device *bdev, int copy_num,
>>   	struct buffer_head *bh;
>>   	struct btrfs_super_block *super;
>>   	u64 bytenr;
>> +	int err;
>>   
>>   	bytenr = btrfs_sb_offset(copy_num);
>>   	if (bytenr + BTRFS_SUPER_INFO_SIZE >= i_size_read(bdev->bd_inode))
>> @@ -3148,6 +3131,22 @@ int btrfs_read_dev_one_super(struct block_device *bdev, int copy_num,
>>   		return -EINVAL;
>>   	}
>>   
>> +	/*
>> +	 * Check the superblock checksum, the type is stored inside.
>> +	 * Pass the whole disk block of size BTRFS_SUPER_INFO_SIZE (4k).
>> +	 */
>> +	err = btrfs_check_super_csum(bh->b_data);
>> +	if (err) {

I am fixing this to if (err < 0) {

>> +		if (err == -EINVAL)
>> +			pr_err("BTRFS error (device %pg): unsupported checksum algorithm",
>> +				bdev);
>> +		else if (err == -EUCLEAN)
>> +			pr_err("BTRFS error (device %pg): superblock checksum mismatch",
>> +				bdev);

  I am also dropping else if to else in v2.

Thanks, Anand


>> +		brelse(bh);
>> +		return err;
>> +	}
>> +
>>   	*bh_ret = bh;
>>   	return 0;
>>   }
>>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

  reply	other threads:[~2018-03-27 22:47 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-26  8:27 [PATCH 0/8] Superblock read and verify cleanups Anand Jain
2018-03-26  8:27 ` [PATCH 1/8] btrfs: cleanup btrfs_check_super_csum() for better code flow Anand Jain
2018-03-27 12:10   ` Nikolay Borisov
2018-03-26  8:27 ` [PATCH 2/8] btrfs: return required error from btrfs_check_super_csum Anand Jain
2018-03-27  8:05   ` Nikolay Borisov
2018-03-27 19:16     ` David Sterba
2018-03-27 20:43       ` Anand Jain
2018-04-05 14:48         ` David Sterba
2018-03-26  8:27 ` [PATCH 3/8] btrfs: cleanup btrfs_read_disk_super() to return std error Anand Jain
2018-03-27  8:07   ` Nikolay Borisov
2018-03-26  8:27 ` [PATCH 4/8] btrfs: make btrfs_check_super_csum() non-static Anand Jain
2018-03-27 12:10   ` Nikolay Borisov
2018-03-26  8:27 ` [PATCH 5/8] btrfs: check if the fsid in the primary sb and copy sb are same Anand Jain
2018-03-27  8:49   ` Nikolay Borisov
2018-03-27 22:06     ` Anand Jain
2018-03-28  6:08       ` Nikolay Borisov
2018-03-28  7:05         ` Anand Jain
2018-03-26  8:27 ` [PATCH 6/8] btrfs: verify checksum when superblock is read for scan Anand Jain
2018-03-27 11:30   ` Nikolay Borisov
2018-03-27 12:09     ` Nikolay Borisov
2018-03-27 23:01       ` Anand Jain
2018-03-28  6:12         ` Nikolay Borisov
2018-03-26  8:27 ` [PATCH 7/8] btrfs: verify checksum for all devices in mount context Anand Jain
2018-03-27 12:21   ` Nikolay Borisov
2018-03-27 22:48     ` Anand Jain [this message]
2018-03-26  8:27 ` [PATCH 8/8] btrfs: drop the redundant invalidate_bdev() Anand Jain

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=01ec84dd-658e-4d04-a332-71f9513cbc3f@oracle.com \
    --to=anand.jain@oracle.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).