From: Nikolay Borisov <nborisov@suse.com>
To: Anand Jain <anand.jain@oracle.com>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH 6/8] btrfs: verify checksum when superblock is read for scan
Date: Wed, 28 Mar 2018 09:12:41 +0300 [thread overview]
Message-ID: <4219f6b9-0e8d-d6a7-1fb8-f526b267e290@suse.com> (raw)
In-Reply-To: <761e4a64-0e33-11a7-b265-3428eb12c626@oracle.com>
On 28.03.2018 02:01, Anand Jain wrote:
>
>
>>>> Test script:
>>>>
>>>> Corrupt primary superblock and check if device scan and mount
>>>> fails:
>>>> mkfs.btrfs -fq /dev/sdc
>>>> dd if=/dev/urandom of=/dev/sdc ibs=1 obs=1 count=1 seek=64K
>>>> btrfs dev scan
>>>> mount /dev/sdb /btrfs
>>>>
>>>> Corrupt secondary superblock and check if device scan and mount
>>>> is succcessful, check for the dmesg for errors.
>>>> mkfs.btrfs -fq /dev/sdc
>>>> dd if=/dev/urandom of=/dev/sdc ibs=1 obs=1 count=1 seek=64K
>>>> btrfs dev scan
>>>> mount /dev/sdb /btrfs
>>>
>>> Have you considered adding fstests, it will be very easy to test for
>>> this behavior?
>
> This is one off kind of bug, not sure if it would value add
> for checking it all the time in xfstests?
>
It's some btrfs-specific behavior which in order to not regress in the
future it will be best to have tests for. IMO whatever we can test
should be tested to ensure maintainability. I think a btrfs-specific
test wouldn't hurt here.
>
>>> Same comment as before regarding string literals splitting across lines.
>
> accepted.
>
>
>>>> + else
>>>> + pr_err("BTRFS error (device %pg): "\
>>>> + "superblock checksum failed, bytenr=%llu",
>>>> + bdev, bytenr);
>>>> + btrfs_release_disk_super(*page);
>>>> + return err;
>>>> + }
>>
>> Also it will be better to have the checksum check after we have verified
>> some basic invariants - that bytenr and magic have sane values.
>
> accepted.
>
> Thanks,
> Anand
>
next prev parent reply other threads:[~2018-03-28 6:12 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 [this message]
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
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=4219f6b9-0e8d-d6a7-1fb8-f526b267e290@suse.com \
--to=nborisov@suse.com \
--cc=anand.jain@oracle.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).