linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shaohua Li <shli@kernel.org>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org
Subject: [GIT PULL] MD update for 4.19-rc1
Date: Mon, 13 Aug 2018 11:45:57 -0700	[thread overview]
Message-ID: <20180813184557.GA8056@kernel.org> (raw)

Hi,
A few MD fixes for 4.19-rc1:
- Several md-cluster fixes from Guoqing
- A data corruption fix from BingJing
- Other cleanups
Please pull!

Thanks,
Shaohua

The following changes since commit 06c85639897cf3ea6a11c5cb6929fb0d9d7efea5:

  Merge tag 'acpi-4.18-rc4' of git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm (2018-07-05 09:52:30 -0700)

are available in the Git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shli/md.git for-next

for you to fetch changes up to d63e2fc804c46e50eee825c5d3a7228e07048b47:

  md/raid5: fix data corruption of replacements after originals dropped (2018-08-02 11:22:06 -0700)

----------------------------------------------------------------
Anna-Maria Gleixner (2):
      drivers/md/raid5: Use irqsave variant of atomic_dec_and_lock()
      drivers/md/raid5: Do not disable irq on release_inactive_stripe_list() call

BingJing Chang (1):
      md/raid5: fix data corruption of replacements after originals dropped

Colin Ian King (1):
      md/r5cache: remove redundant pointer bio

Guoqing Jiang (3):
      md-cluster: clear another node's suspend_area after the copy is finished
      md-cluster: show array's status more accurate
      md-cluster: don't send msg if array is closing

 drivers/md/md-cluster.c  | 47 +++++++++++++++++++++++++++++++++++------------
 drivers/md/md.c          | 17 +++++++++++++++++
 drivers/md/md.h          |  1 +
 drivers/md/raid5-cache.c |  2 --
 drivers/md/raid5.c       | 12 ++++++++----
 5 files changed, 61 insertions(+), 18 deletions(-)

                 reply	other threads:[~2018-08-13 18:45 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20180813184557.GA8056@kernel.org \
    --to=shli@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=torvalds@linux-foundation.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).