From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Frieder Schrempf <frieder.schrempf@kontron.de>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
sashal@kernel.org, linux-mtd@lists.infradead.org,
linux-kernel@vger.kernel.org, vigneshr@ti.com,
miquel.raynal@bootlin.com,
Yoshio Furuyama <ytc-mb-yfuruyama7@kioxia.com>,
richard@nod.at, Stoll Eberhard <Eberhard.Stoll@kontron.de>
Subject: Re: [PATCH v2 1/2] Fix corner case in bad block table handling.
Date: Mon, 24 Jan 2022 15:29:19 +0100 [thread overview]
Message-ID: <Ye63v1ypd0H7FYyD@kroah.com> (raw)
In-Reply-To: <ccc99c80-6771-4f04-11d9-752b7b13a5a4@kontron.de>
On Mon, Jan 24, 2022 at 03:11:14PM +0100, Frieder Schrempf wrote:
> Hi Greg, Sasha,
>
> just a gentle ping for the backport request below.
>
> Thanks!
>
> Am 11.01.22 um 16:33 schrieb Frieder Schrempf:
> > Hi stable maintainers,
> >
> > On 06.04.21 03:47, Yoshio Furuyama wrote:
> >> From: "Doyle, Patrick" <pdoyle@irobot.com>
> >>
> >> In the unlikely event that both blocks 10 and 11 are marked as bad (on a
> >> 32 bit machine), then the process of marking block 10 as bad stomps on
> >> cached entry for block 11. There are (of course) other examples.
> >>
> >> Signed-off-by: Patrick Doyle <pdoyle@irobot.com>
> >> Reviewed-by: Richard Weinberger <richard@nod.at>
> >
> > We have systems on which this patch fixes real failures. Could you
> > please add the upstream patch fd0d8d85f723 ("mtd: nand: bbt: Fix corner
> > case in bad block table handling") to the stable queues for 4.19, 5.4, 5.10?
> >
> > Thanks!
> >
> > Cc: stable@vger.kernel.org
> > Fixes: 9c3736a3de21 ("mtd: nand: Add core infrastructure to deal with
> > NAND devices")
Odd, I did not see this anywhere in my inbox.
Now queued up, thanks.
greg k-h
next prev parent reply other threads:[~2022-01-24 14:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-06 1:46 [PATCH v2 0/2] Fix corner case in bad block table handling Yoshio Furuyama
2021-04-06 1:47 ` [PATCH v2 1/2] " Yoshio Furuyama
2021-05-10 10:52 ` Miquel Raynal
2022-01-11 15:33 ` Frieder Schrempf
2022-01-24 14:11 ` Frieder Schrempf
2022-01-24 14:29 ` Greg Kroah-Hartman [this message]
2021-04-06 1:47 ` [PATCH v2 2/2] Fix the issue for clearing status process Yoshio Furuyama
2021-04-07 9:04 ` Miquel Raynal
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=Ye63v1ypd0H7FYyD@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Eberhard.Stoll@kontron.de \
--cc=frieder.schrempf@kontron.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=sashal@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vigneshr@ti.com \
--cc=ytc-mb-yfuruyama7@kioxia.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).