From: NeilBrown <neilb@suse.com>
To: Shaohua Li <shli@kernel.org>
Cc: linux-raid@vger.kernel.org, Coly Li <colyli@suse.de>
Subject: [md PATCH 0/2] Make it possible to disable create_on_open semantics.
Date: Wed, 12 Apr 2017 16:26:12 +1000 [thread overview]
Message-ID: <149197804398.19936.12809382889200123725.stgit@noble> (raw)
Currently, opening an md /dev node will create the array object.
This makes it hard to destroy the object as udev will typically
re-open the device node when handling REMOVE events.
The "new_array" module parameter was created to work towards avoiding
this problem, and it can be used when
CREATE names=yes
is given in /etc/mdadm.conf.
How this doesn't currently support names like "md%d", which lots of
people use and expect, so we need more work before we can transition
away from create_on_open.
These patches add support to "new_array" so that md%d devices
can be created. This will make it, once again, possible to have
md%d devices with numbers > 511. (3.17 make this impossible).
An enhancement to mdadm that uses this will cause new_array to always
be used (where available), and we can then disable create_on_open
completely (after suitable transition periods).
NeilBrown
---
NeilBrown (2):
md: allow creation of mdNNN arrays via md_mod/parameters/new_array
md: support disabling of create-on-open semantics.
drivers/md/md.c | 48 +++++++++++++++++++++++++++++++++++++++++-------
1 file changed, 41 insertions(+), 7 deletions(-)
--
Signature
next reply other threads:[~2017-04-12 6:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 6:26 NeilBrown [this message]
2017-04-12 6:26 ` [md PATCH 2/2] md: support disabling of create-on-open semantics NeilBrown
2017-04-12 14:49 ` Coly Li
2017-04-12 6:26 ` [md PATCH 1/2] md: allow creation of mdNNN arrays via md_mod/parameters/new_array NeilBrown
2017-04-12 14:48 ` Coly Li
2017-04-12 19:24 ` [md PATCH 0/2] Make it possible to disable create_on_open semantics 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=149197804398.19936.12809382889200123725.stgit@noble \
--to=neilb@suse.com \
--cc=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=shli@kernel.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