All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: NeilBrown <neilb@suse.com>
Cc: Linux Raid <linux-raid@vger.kernel.org>
Subject: Re: [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed.
Date: Wed, 27 Sep 2017 17:30:46 -0400	[thread overview]
Message-ID: <378e1fe4-6844-b6f4-3242-33657a0b0219@gmail.com> (raw)
In-Reply-To: <87y3p372b0.fsf@notabene.neil.brown.name>

On 09/25/2017 01:52 AM, NeilBrown wrote:
> 
> Creating an array by opening a block-device with major number of 9
> will transparently load the md module if needed.
> Creating an array by opening
>     /sys/module/md_mod/parameters/new_array
> and writing to it won't, it will just fail if md_mod isn't loaded.
> 
> So when opening that file fails with ENOENT, run "modprobe md_mod" and
> try again.
> 
> This fixes a bug whereby if you have "CREATE names=yes" in mdadm.conf,
> and the md modules isn't loaded, then creating or assembling an
> array will not honor the "names=yes" configuration.
> 
> Signed-off-by: NeilBrown <neilb@suse.com>
> ---
>   mdopen.c | 4 ++++
>   1 file changed, 4 insertions(+)

Applied!

Thanks,
Jes


  parent reply	other threads:[~2017-09-27 21:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-25  5:52 [mdadm PATCH] mdopen: call "modprobe md_mod" if it might be needed NeilBrown
2017-09-25 15:26 ` John Stoffel
2017-09-25 23:50   ` NeilBrown
2017-09-26 15:11     ` Jes Sorensen
2017-09-26 19:12       ` Wols Lists
2017-09-26 20:55         ` John Stoffel
2017-09-27 21:30 ` Jes Sorensen [this message]
     [not found] ` <cba5f77f-d6de-7a6b-35b0-70b7c56eb3f7@suse.com>
2017-10-10 20:16   ` NeilBrown
2017-10-11  7:39     ` Zhilong Liu
2017-10-12  0:06       ` NeilBrown
2017-10-12  3:55         ` Zhilong Liu
2017-10-12  8:48           ` NeilBrown
2017-10-13  9:16             ` Zhilong Liu
2017-10-15 22:41               ` NeilBrown
2017-10-12  9:55         ` Wols Lists

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=378e1fe4-6844-b6f4-3242-33657a0b0219@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.