linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: [PATCH v3 0/2] Preparatory to add the csum check in the scan context
Date: Mon, 26 Mar 2018 14:40:28 +0800	[thread overview]
Message-ID: <59fb1970-7bcd-c5f0-43f6-e7d5adb3b07d@oracle.com> (raw)
In-Reply-To: <20180321081454.31560-1-anand.jain@oracle.com>



  Pls, ignore this bunch as I have included this with other cleanups.

Thanks, Anand


On 03/21/2018 04:14 PM, Anand Jain wrote:
> v2->v3:
>   1/2: Keep the check %(csum_type >= ARRAY_SIZE(btrfs_csum_sizes))
>        because it is inline to support future expansion, further
>        btrfs-progs is already copied it.
>   2/2: Drop pr_err for default error which won't be possible.
> 
> v1->v2:
>    Merge 2/3 and 3/3
>    Use -EUCLEAN for csum mismatch
>    Move the error logging to the parent function
>    Drop the struct btrfs_fsinfo as the argument for
>          btrfs_check_super_csum()
>    Do not make btrfs_check_super_csum() nonstatic here, it will be part
>          of the patchset which will use the csum in the scan context
> 
> Anand Jain (2):
>    btrfs: cleanup btrfs_check_super_csum() to check the csum_type to the
>      type
>    btrfs: return required error from btrfs_check_super_csum
> 
>   fs/btrfs/disk-io.c | 53 ++++++++++++++++++++++++++---------------------------
>   1 file changed, 26 insertions(+), 27 deletions(-)
> 

      parent reply	other threads:[~2018-03-26  6:38 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-20  9:53 [PATCH 0/3] Preparatory to add the csum check in the scan context Anand Jain
2018-03-20  9:53 ` [PATCH 1/3] btrfs: cleanup btrfs_check_super_csum() to check the csum_type to the type Anand Jain
2018-03-20 10:11   ` Nikolay Borisov
2018-03-20 10:12     ` Nikolay Borisov
2018-03-20  9:53 ` [PATCH 2/3] btrfs: return required error from btrfs_check_super_csum Anand Jain
2018-03-20 10:13   ` Nikolay Borisov
2018-03-20 22:23     ` Anand Jain
2018-03-21  2:37     ` Anand Jain
2018-03-21  3:01       ` Anand Jain
2018-03-20  9:53 ` [PATCH 3/3] btrfs: refactor btrfs_check_super_csum() for scan Anand Jain
2018-03-20 11:10   ` Nikolay Borisov
2018-03-20 22:32     ` Anand Jain
2018-03-21  8:14 ` [PATCH v3 0/2] Preparatory to add the csum check in the scan context Anand Jain
2018-03-21  8:14   ` [PATCH v3 1/2] btrfs: cleanup btrfs_check_super_csum() to check the csum_type to the type Anand Jain
2018-03-21  8:14   ` [PATCH v3 2/2] btrfs: return required error from btrfs_check_super_csum Anand Jain
2018-03-26  6:40   ` Anand Jain [this message]

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=59fb1970-7bcd-c5f0-43f6-e7d5adb3b07d@oracle.com \
    --to=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).