linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Zhao Lei <zhaolei@cn.fujitsu.com>
To: <linux-btrfs@vger.kernel.org>
Cc: Zhao Lei <zhaolei@cn.fujitsu.com>
Subject: [PATCH 0/5] btrfs: scrub: setup all fields for sblock_to_check
Date: Mon, 24 Aug 2015 23:34:15 +0800	[thread overview]
Message-ID: <cover.1440430437.git.zhaolei@cn.fujitsu.com> (raw)

scrub_setup_recheck_block() isn't setup all necessary fields for
sblock_to_check because history reason.

So current code need more arguments in severial functions,
and more local variables, just to passing these lacked values to
necessary place.

[PATCH 1/5] setup above fields for sblock_to_check, it makes other
code simple(done in [PATCH 2..5]).

Zhao Lei (5):
  btrfs: scrub: setup all fields for sblock_to_check
  btrfs: Reset sblock->xxx_error stats before calling
    scrub_recheck_block_checksum
  btrfs: Use scrub_checksum_data and scrub_checksum_tree_block for
    scrub_recheck_block_checksum
  btrfs: Reduce unnecessary arguments in scrub_recheck_block
  btrfs: Remove len argument from scrub_find_csum

 fs/btrfs/scrub.c | 169 +++++++++++++++++++------------------------------------
 1 file changed, 57 insertions(+), 112 deletions(-)

-- 
1.8.5.1


             reply	other threads:[~2015-08-24 15:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24 15:34 Zhao Lei [this message]
2015-08-24 15:34 ` [PATCH 1/5] btrfs: scrub: setup all fields for sblock_to_check Zhao Lei
2015-08-24 15:34 ` [PATCH 2/5] btrfs: Reset sblock->xxx_error stats before calling scrub_recheck_block_checksum Zhao Lei
2015-08-24 15:34 ` [PATCH 3/5] btrfs: Use scrub_checksum_data and scrub_checksum_tree_block for scrub_recheck_block_checksum Zhao Lei
2015-08-24 15:34 ` [PATCH 4/5] btrfs: Reduce unnecessary arguments in scrub_recheck_block Zhao Lei
2015-08-24 15:34 ` [PATCH 5/5] btrfs: Remove len argument from scrub_find_csum Zhao Lei

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=cover.1440430437.git.zhaolei@cn.fujitsu.com \
    --to=zhaolei@cn.fujitsu.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).