All of lore.kernel.org
 help / color / mirror / Atom feed
From: Qu Wenruo <quwenruo@cn.fujitsu.com>
To: <dsterba@suse.cz>, <bo.li.liu@oracle.com>,
	<linux-btrfs@vger.kernel.org>, <vegard.nossum@oracle.com>,
	<dsterba@suse.com>
Subject: Re: [PATCH 1/2] Btrfs: add more valid checks for superblock
Date: Mon, 9 May 2016 09:31:37 +0800	[thread overview]
Message-ID: <47023701-8dd4-6c38-b242-230a372890e7@cn.fujitsu.com> (raw)
In-Reply-To: <20160506143529.GD29353@twin.jikos.cz>



David Sterba wrote on 2016/05/06 16:35 +0200:
> On Thu, May 05, 2016 at 09:08:54AM +0800, Qu Wenruo wrote:
>>>> An early check can compare against some reasonable value, but the
>>>> total_bytes value must be equal to the sum of all device sizes
>>>> (disk_total_bytes). I'm not sure if we have enough information to verify
>>>> that at this point though.
>>>
>>> That's what I had in mind, the problem is that only the first device information is recorded in superblock.
>>>
>>> At this moment We have device_num but we don't know the size of other devices.
>>>
>>> Thanks,
>>>
>>> -liubo
>>>
>>>
>> What about error out if we found sb->total_bytes <
>> sb->dev_item->total_bytes?
>>
>> As we are just doing early check, no need to be comprehensive, but spot
>> obvious problem.
>
> Ok.
>
>> For exact device_num and sb->total_bytes, we may do post check when
>> device tree are loaded?
>> Splitting early_check() and post_check() seems valid for me.
>> (Also I prefer post_check() just warning, not forced exit)
>
> Why just warning? Superblock total_bytes and device sizes must be
> correct, otherwise all sorts of operations can fail randomly.
>
>
Because if we exit, we can't even do fsck.

Maybe we need a new flag to control whether exit or warn at post_check().

Thanks,
Qu



  reply	other threads:[~2016-05-09  1:31 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-02 18:15 [PATCH 1/2] Btrfs: add more valid checks for superblock Liu Bo
2016-05-02 18:15 ` [PATCH 2/2] Btrfs: add valid checks for chunk loading Liu Bo
2016-05-03  1:12   ` Qu Wenruo
2016-05-03 23:36     ` Liu Bo
2016-05-05  1:03       ` Qu Wenruo
2016-05-03  5:53   ` Anand Jain
2016-05-03 23:33     ` Liu Bo
2016-05-04 13:56   ` David Sterba
2016-05-13 23:57     ` Liu Bo
2016-05-17 13:37       ` David Sterba
2016-05-02 18:23 ` [PATCH 1/2] Btrfs: add more valid checks for superblock Liu Bo
2016-05-03  1:02 ` Qu Wenruo
2016-05-03 23:32   ` Liu Bo
2016-05-04 13:23   ` David Sterba
2016-05-04 17:44     ` Liu Bo
2016-05-05  1:08       ` Qu Wenruo
2016-05-06 14:35         ` David Sterba
2016-05-09  1:31           ` Qu Wenruo [this message]
2016-05-13 18:14             ` Liu Bo
2016-05-13 23:42               ` Qu Wenruo
2016-05-17 13:47                 ` David Sterba
2016-05-04 13:29 ` David Sterba
2016-05-04 17:40   ` Liu Bo
2016-05-06 14:39     ` 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=47023701-8dd4-6c38-b242-230a372890e7@cn.fujitsu.com \
    --to=quwenruo@cn.fujitsu.com \
    --cc=bo.li.liu@oracle.com \
    --cc=dsterba@suse.com \
    --cc=dsterba@suse.cz \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=vegard.nossum@oracle.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.