linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
	linux RAID <linux-raid@vger.kernel.org>,
	Peter Koch <mdraid.pkoch@dfgh.net>,
	Dan Williams <dan.j.williams@intel.com>
Subject: [GIT PULL REQUEST] bugfixes for md.
Date: Tue, 19 Aug 2014 17:25:18 +1000	[thread overview]
Message-ID: <20140819172518.63aaeea2@notabene.brown> (raw)

[-- Attachment #1: Type: text/plain, Size: 1306 bytes --]


Here are the bug-fixes I promised :-)
Funny how you start looking for one and other start appearing.

Thanks,
NeilBrown


The following changes since commit 7d1311b93e58ed55f3a31cc8f94c4b8fe988a2b9:

  Linux 3.17-rc1 (2014-08-16 10:40:26 -0600)

are available in the git repository at:

  git://neil.brown.name/md/ tags/md/3.17-fixes

for you to fetch changes up to cb8b12b5d81cf8522076f99a90bc3b795825c3b3:

  md/raid10: always initialise ->state on newly allocated r10_bio (2014-08-19 17:20:27 +1000)

----------------------------------------------------------------
md bugfixes for 3.17

 - raid6 data corruption during recovery
 - raid6 livelock
 - raid10 memory leaks.

----------------------------------------------------------------
NeilBrown (6):
      md/raid5: avoid livelock caused by non-aligned writes.
      md/raid6: avoid data corruption during recovery of double-degraded RAID6
      md/raid10: fix memory leak when reshaping a RAID10.
      md/raid10: Fix memory leak when raid10 reshape completes.
      md/raid10: avoid memory leak on error path during reshape.
      md/raid10: always initialise ->state on newly allocated r10_bio

 drivers/md/raid10.c | 7 ++++++-
 drivers/md/raid5.c  | 4 +++-
 2 files changed, 9 insertions(+), 2 deletions(-)

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

                 reply	other threads:[~2014-08-19  7:25 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=20140819172518.63aaeea2@notabene.brown \
    --to=neilb@suse.de \
    --cc=dan.j.williams@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=mdraid.pkoch@dfgh.net \
    --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).