From: NeilBrown <neilb@suse.de>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Xiao Ni <xni@redhat.com>, jiao hui <jiaohui@bwstor.com.cn>,
linux RAID <linux-raid@vger.kernel.org>,
lkml <linux-kernel@vger.kernel.org>
Subject: [GIT PULL REQUEST] md updates for 3.17
Date: Mon, 11 Aug 2014 15:07:46 +1000 [thread overview]
Message-ID: <20140811150746.448ec9e4@notabene.brown> (raw)
[-- Attachment #1: Type: text/plain, Size: 1576 bytes --]
The following changes since commit 64aa90f26c06e1cb2aacfb98a7d0eccfbd6c1a91:
Linux 3.16-rc7 (2014-07-27 12:41:55 -0700)
are available in the git repository at:
git://neil.brown.name/md/ tags/md/3.17
for you to fetch changes up to d66b1b395a59027a1c054e1fc57d582cb4194491:
md: don't allow bitmap file to be added to raid0/linear. (2014-08-08 15:43:20 +1000)
I've nearly isolated another bug - raid6 can sometime get corrupt during
recovery. Once that is properly understood and tested I'll send it separately.
Thanks,
NeilBrown
----------------------------------------------------------------
md updates for 3.17
Most interesting is that md devices (major == 9) with
minor numbers of 512 or more will no longer be created
simply by opening a block device file. They can only
be created by writing to
/sys/module/md_mod/parameters/new_array
The 'auto-create-on-open' semantic is cumbersome and we
need to start moving away from it.
----------------------------------------------------------------
NeilBrown (4):
md/raid1,raid10: always abort recover on write error.
md: disable probing for md devices 512 and over.
md/raid0: check for bitmap compatability when changing raid levels.
md: don't allow bitmap file to be added to raid0/linear.
Xiao Ni (1):
md: Recovery speed is wrong
drivers/md/md.c | 13 +++++++------
drivers/md/raid0.c | 6 ++++++
drivers/md/raid1.c | 8 ++++----
drivers/md/raid10.c | 11 +++++------
4 files changed, 22 insertions(+), 16 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]
reply other threads:[~2014-08-11 5:07 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=20140811150746.448ec9e4@notabene.brown \
--to=neilb@suse.de \
--cc=jiaohui@bwstor.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=xni@redhat.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).