[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <318ff554-0694-64e1-72bd-d941a775a16f@trained-monkey.org>
Date: Sun, 19 Mar 2023 12:36:06 -0400
From: Jes Sorensen <jes@...ined-monkey.org>
To: NeilBrown <neilb@...e.de>
Cc: Mariusz Tkaczyk <mariusz.tkaczyk@...ux.intel.com>,
Song Liu <song@...nel.org>,
Linux regressions mailing list <regressions@...ts.linux.dev>,
linux-raid <linux-raid@...r.kernel.org>,
LKML <linux-kernel@...r.kernel.org>,
Nikolay Kichukov <hijacker@...um.net>
Subject: Re: [PATCH - mdadm] mdopen: always try create_named_array()
On 3/13/23 20:06, NeilBrown wrote:
>
> mdopen() will use create_named_array() to ask the kernel to create the
> given md array, but only if it is given a number or name.
> If it is NOT given a name and is required to choose one itself using
> find_free_devnm() it does NOT use create_named_array().
>
> On kernels with CONFIG_BLOCK_LEGACY_AUTOLOAD not set, this can result in
> failure to assemble an array. This can particularly seen when the
> "name" of the array begins with a host name different to the name of the
> host running the command.
>
> So add the missing call to create_named_array().
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=217074
> Signed-off-by: NeilBrown <neilb@...e.de>
Applied!
Thanks,
Jes
Powered by blists - more mailing lists