From: Mariusz Tkaczyk <mariusz.tkaczyk@linux.intel.com>
To: Mateusz Grzonka <mateusz.grzonka@intel.com>
Cc: linux-raid@vger.kernel.org, jes@trained-monkey.org
Subject: Re: [PATCH v2] Create: Fix checking for container in update_metadata
Date: Thu, 23 Mar 2023 16:29:01 +0100 [thread overview]
Message-ID: <20230323162901.00005b0a@linux.intel.com> (raw)
In-Reply-To: <20230323115000.25364-1-mateusz.grzonka@intel.com>
Hi Jes,
Please merge this to unblock our upstream testing :)
Thanks,
Mariusz
On Thu, 23 Mar 2023 12:50:00 +0100
Mateusz Grzonka <mateusz.grzonka@intel.com> wrote:
> The commit 8a4ce2c05386 ("Create: Factor out add_disks() helpers")
> introduced a regression that caused timeouts and udev failing to create
> links.
>
> Steps to reproduce the issue were as following:
> $ mdadm -CR imsm -e imsm -n4 /dev/nvme[0-3]n1
> $ mdadm -CR vol -l5 -n4 /dev/nvme[0-3]n1 --assume-clean
>
> I found the check for container was wrong because negation was missing.
>
> Fixes: 8a4ce2c05386 ("Create: Factor out add_disks() helpers")
> Signed-off-by: Mateusz Grzonka <mateusz.grzonka@intel.com>
> ---
> Create.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Create.c b/Create.c
> index bbe9e13d..0911bf92 100644
> --- a/Create.c
> +++ b/Create.c
> @@ -328,7 +328,7 @@ static int update_metadata(int mdfd, struct shape *s,
> struct supertype *st,
> * again returns container info.
> */
> st->ss->getinfo_super(st, &info_new, NULL);
> - if (st->ss->external && is_container(s->level) &&
> + if (st->ss->external && !is_container(s->level) &&
> !same_uuid(info_new.uuid, info->uuid, 0)) {
> map_update(map, fd2devnm(mdfd),
> info_new.text_version,
next prev parent reply other threads:[~2023-03-23 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:50 [PATCH v2] Create: Fix checking for container in update_metadata Mateusz Grzonka
2023-03-23 15:29 ` Mariusz Tkaczyk [this message]
2023-03-23 16:44 ` Jes Sorensen
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=20230323162901.00005b0a@linux.intel.com \
--to=mariusz.tkaczyk@linux.intel.com \
--cc=jes@trained-monkey.org \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz.grzonka@intel.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.