Linux RAID subsystem development
 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, neilb@suse.de
Subject: [GIT PULL] MD update for 4.9-rc3
Date: Fri, 4 Nov 2016 17:43:51 -0700	[thread overview]
Message-ID: <20161105004351.ck7ikmhhqdtel6qe@kernel.org> (raw)

Hi Linus,

Please pull MD changes for 4.9-rc3. There are several bug fixes queued:
- Fix raid5-cache recovery bugs
- Fix discard IO error handling for raid1/10
- Fix array sync writes bogus position to superblock
- Fix IO error handling for raid array with external metadata

Thanks,
Shaohua


The following changes since commit 07d9a380680d1c0eb51ef87ff2eab5c994949e69:

  Linux 4.9-rc2 (2016-10-23 17:10:14 -0700)

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/shli/md.git tags/md/4.9-rc3

for you to fetch changes up to 1217e1d1999ed6c9c1e1b1acae0a74ab70464ae2:

  md: be careful not lot leak internal curr_resync value into metadata. -- (all) (2016-10-28 22:04:05 -0700)

----------------------------------------------------------------
NeilBrown (1):
      md: be careful not lot leak internal curr_resync value into metadata. -- (all)

Shaohua Li (3):
      RAID1: ignore discard error
      RAID10: ignore discard error
      raid5-cache: correct condition for empty metadata write

Tomasz Majchrzak (2):
      md: report 'write_pending' state when array in sync
      raid1: handle read error also in readonly mode

Zhengyuan Liu (2):
      md/raid5: initialize next_checkpoint field before use
      md/raid5: write an empty meta-block when creating log super-block

 drivers/md/md.c          | 10 +++++-----
 drivers/md/raid1.c       | 26 +++++++++++++++-----------
 drivers/md/raid10.c      |  7 +++++--
 drivers/md/raid5-cache.c |  6 +++++-
 4 files changed, 30 insertions(+), 19 deletions(-)

                 reply	other threads:[~2016-11-05  0:43 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=20161105004351.ck7ikmhhqdtel6qe@kernel.org \
    --to=shli@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --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