From: Qu Wenruo <quwenruo.btrfs@gmx.com>
To: Anand Jain <anand.jain@oracle.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Do super block verification before writing it to disk
Date: Mon, 16 Apr 2018 21:00:38 +0800 [thread overview]
Message-ID: <8cc34db9-0d09-38de-ac59-ed2be758de58@gmx.com> (raw)
In-Reply-To: <59af2ff4-b8d9-c1df-2053-c180c5533d2d@oracle.com>
[-- Attachment #1.1: Type: text/plain, Size: 3882 bytes --]
On 2018年04月16日 20:55, Anand Jain wrote:
>
>
> On 04/16/2018 10:02 AM, Qu Wenruo wrote:
>> There are already 2 reports about strangely corrupted super blocks,
>> where csum type and incompat flags get some obvious garbage, but csum
>> still matches and all other vitals are correct.
>>
>> This normally means some kernel memory corruption happens, although the
>> cause is unknown, at least detect it and prevent further corruption.
>>
>> Signed-off-by: Qu Wenruo <wqu@suse.com>
>> ---
>
> Can you help point those 2 cases here?
Did you mean the reported-by tags?
If so, no problem.
Thanks,
Qu
>
> Thanks, Anand
>
>
>> fs/btrfs/disk-io.c | 24 ++++++++++++++++++++----
>> 1 file changed, 20 insertions(+), 4 deletions(-)
>>
>> diff --git a/fs/btrfs/disk-io.c b/fs/btrfs/disk-io.c
>> index 23803102aa0d..10d814f03f13 100644
>> --- a/fs/btrfs/disk-io.c
>> +++ b/fs/btrfs/disk-io.c
>> @@ -68,7 +68,8 @@
>> static const struct extent_io_ops btree_extent_io_ops;
>> static void end_workqueue_fn(struct btrfs_work *work);
>> static void free_fs_root(struct btrfs_root *root);
>> -static int btrfs_check_super_valid(struct btrfs_fs_info *fs_info);
>> +static int btrfs_check_super_valid(struct btrfs_fs_info *fs_info,
>> + struct btrfs_super_block *sb);
>> static void btrfs_destroy_ordered_extents(struct btrfs_root *root);
>> static int btrfs_destroy_delayed_refs(struct btrfs_transaction *trans,
>> struct btrfs_fs_info *fs_info);
>> @@ -2680,7 +2681,7 @@ int open_ctree(struct super_block *sb,
>> memcpy(fs_info->fsid, fs_info->super_copy->fsid,
>> BTRFS_FSID_SIZE);
>> - ret = btrfs_check_super_valid(fs_info);
>> + ret = btrfs_check_super_valid(fs_info, fs_info->super_copy);
>> if (ret) {
>> btrfs_err(fs_info, "superblock contains fatal errors");
>> err = -EINVAL;
>> @@ -3575,6 +3576,21 @@ int write_all_supers(struct btrfs_fs_info
>> *fs_info, int max_mirrors)
>> sb = fs_info->super_for_commit;
>> dev_item = &sb->dev_item;
>> + /* Do extra check on the sb to be written */
>> + ret = btrfs_check_super_valid(fs_info, sb);
>> + if (ret) {
>> + btrfs_err(fs_info, "fatal superblock corrupted detected");
>> + return -EUCLEAN;
>> + }
>> + /*
>> + * Unknown incompat flags can't be mounted, so newly developed flags
>> + * means corruption
>> + */
>> + if (btrfs_super_incompat_flags(sb) & ~BTRFS_FEATURE_INCOMPAT_SUPP) {
>> + btrfs_err(fs_info, "fatal superblock corrupted detected");
>> + return -EUCLEAN;
>> + }
>> +
>> mutex_lock(&fs_info->fs_devices->device_list_mutex);
>> head = &fs_info->fs_devices->devices;
>> max_errors = btrfs_super_num_devices(fs_info->super_copy) - 1;
>> @@ -3985,9 +4001,9 @@ int btrfs_read_buffer(struct extent_buffer *buf,
>> u64 parent_transid, int level,
>> level, first_key);
>> }
>> -static int btrfs_check_super_valid(struct btrfs_fs_info *fs_info)
>> +static int btrfs_check_super_valid(struct btrfs_fs_info *fs_info,
>> + struct btrfs_super_block *sb)
>> {
>> - struct btrfs_super_block *sb = fs_info->super_copy;
>> u64 nodesize = btrfs_super_nodesize(sb);
>> u64 sectorsize = btrfs_super_sectorsize(sb);
>> int ret = 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
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-04-16 13:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 2:02 [PATCH] btrfs: Do super block verification before writing it to disk Qu Wenruo
2018-04-16 12:55 ` Anand Jain
2018-04-16 13:00 ` Qu Wenruo [this message]
2018-04-16 19:03 ` David Sterba
2018-04-16 19:02 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 1:47 [PATCH v3] " Qu Wenruo
2018-04-17 9:05 ` [PATCH] " Anand Jain
2018-04-17 9:58 ` Qu Wenruo
2018-04-17 14:32 ` Anand Jain
2018-04-17 14:44 ` 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=8cc34db9-0d09-38de-ac59-ed2be758de58@gmx.com \
--to=quwenruo.btrfs@gmx.com \
--cc=anand.jain@oracle.com \
--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