linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shli@fb.com>
To: linux-raid@vger.kernel.org
Cc: Kernel-team@fb.com, songliubraving@fb.com, neilb@suse.de
Subject: [PATCH 0/4]raid5-cache: fix journal hotadd
Date: Tue, 5 Jan 2016 13:26:00 -0800	[thread overview]
Message-ID: <cover.1452028077.git.shli@fb.com> (raw)

Hi Neil,

This patch set fix some issues for journal disk hotadd, mainly for raid array
which isn't created with journal support. If there are write IO running in the
array when journal disk is adding, the write IO isn't protected by journal (eg,
expose write hole issue), but this is unavoidable.

Thanks,
Shaohua

Shaohua Li (4):
  raid5-cache: use rcu api to access r5conf->log
  raid5-cache: avoid write failure for journal hotadd
  raid5-cache: handle flush request for journal hotadd
  raid5-cache: handle batch stripe for journal hotadd

 drivers/md/md.c          | 10 +++++++-
 drivers/md/md.h          |  2 ++
 drivers/md/raid5-cache.c | 61 +++++++++++++++++++++++++++++++++++++++---------
 drivers/md/raid5.c       | 20 ++++++++--------
 drivers/md/raid5.h       | 10 ++++----
 5 files changed, 76 insertions(+), 27 deletions(-)

-- 
2.4.6


             reply	other threads:[~2016-01-05 21:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-05 21:26 Shaohua Li [this message]
2016-01-05 21:26 ` [PATCH 1/4] raid5-cache: use rcu api to access r5conf->log Shaohua Li
2016-01-06  1:04   ` NeilBrown
2016-01-05 21:26 ` [PATCH 2/4] raid5-cache: avoid write failure for journal hotadd Shaohua Li
2016-01-06  1:03   ` NeilBrown
2016-01-05 21:26 ` [PATCH 3/4] raid5-cache: handle flush request " Shaohua Li
2016-01-06  1:12   ` NeilBrown
2016-01-06  1:47     ` Shaohua Li
2016-01-06  2:07       ` NeilBrown
2016-01-05 21:26 ` [PATCH 4/4] raid5-cache: handle batch stripe " Shaohua Li

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.1452028077.git.shli@fb.com \
    --to=shli@fb.com \
    --cc=Kernel-team@fb.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=songliubraving@fb.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;
as well as URLs for NNTP newsgroup(s).