[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025121700-pedicure-reckless-65b9@gregkh>
Date: Wed, 17 Dec 2025 15:04:46 +0100
From: Greg KH <gregkh@...uxfoundation.org>
To: linan666@...weicloud.com
Cc: stable@...r.kernel.org, song@...nel.org, yukuai3@...wei.com,
linux-raid@...r.kernel.org, linux-kernel@...r.kernel.org,
yangerkun@...wei.com, yi.zhang@...wei.com
Subject: Re: [PATCH stable/6.18-6.17] md: add check_new_feature module
parameter
On Wed, Dec 17, 2025 at 09:05:13PM +0800, linan666@...weicloud.com wrote:
> From: Li Nan <linan122@...wei.com>
>
> commit 9c47127a807da3e36ce80f7c83a1134a291fc021 upstream.
>
> Raid checks if pad3 is zero when loading superblock from disk. Arrays
> created with new features may fail to assemble on old kernels as pad3
> is used.
>
> Add module parameter check_new_feature to bypass this check.
This is a new feature, why does it need to go to stable kernels?
And a module parameter? Ugh, this isn't the 1990's anymore, this is not
good and will be a mess over time (think multiple devices...)
thanks,
greg k-h
Powered by blists - more mailing lists