All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pascal Hambourg <pascal@plouf.fr.eu.org>
Cc: stable@vger.kernel.org
Subject: Re: md/raid0: Ignore RAID0 layout if the second zone has only one device
Date: Mon, 13 Jun 2022 11:03:51 +0200	[thread overview]
Message-ID: <Yqb9d8O/DGCiuiYA@kroah.com> (raw)
In-Reply-To: <9257c1c4-d052-9e05-9016-8321c2cc47c6@plouf.fr.eu.org>

On Sat, Jun 11, 2022 at 11:14:38AM +0200, Pascal Hambourg wrote:
> Please apply
> Upstream commit ea23994edc4169bd90d7a9b5908c6ccefd82fa40
> to kernel versions 4.14, 4.19, 5.4 and above.
> 
> Reason:
> Commits c84a1372df929033cb1a0441fb57bd3932f39ac9 "md/raid0: avoid RAID0 data
> corruption due to layout confusion." and
> 33f2c35a54dfd75ad0e7e86918dcbe4de799a56c "md: add feature flag
> MD_FEATURE_RAID0_LAYOUT" added handling of original and alternate layouts of
> RAID0 arrays with members of different sizes. However they introduced a
> regression: assembly of such RAID0 array fails if the per-array or default
> layout is not defined even when the layout is irrelevant and can be safely
> ignored. One common case is when the RAID0 array is composed of two members
> of different sizes because the disk or partition sizes are slightly
> different. This patch aims to fix this regression.
> 
> Newer versions of mdadm can set a per-array RAID0 layout but some stable
> distributions such as Debian 10 ship an older version of mdadm which does
> not handle RAID0 layouts and a kernel series (4.19.y) which now includes the
> backported commits. As a result, assembly fails after the kernel upgrade
> unless the default layout is defined with a kernel parameter.
> 
> Related Debian bug reports :
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=944676
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=954816

Now queued up, thanks.

greg k-h

      reply	other threads:[~2022-06-13  9:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  9:14 md/raid0: Ignore RAID0 layout if the second zone has only one device Pascal Hambourg
2022-06-13  9:03 ` Greg KH [this message]

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=Yqb9d8O/DGCiuiYA@kroah.com \
    --to=greg@kroah.com \
    --cc=pascal@plouf.fr.eu.org \
    --cc=stable@vger.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 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.