From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Felix Fietkau <nbd@nbd.name>, stable@vger.kernel.org
Subject: Re: [PATCH] Revert "mtd: spinand: Fix OOB read"
Date: Tue, 5 Jan 2021 11:40:35 +0100 [thread overview]
Message-ID: <20210105114035.2c766901@xps13> (raw)
In-Reply-To: <X/Q//pErSOfQj/Gd@kroah.com>
Hello,
Greg KH <gregkh@linuxfoundation.org> wrote on Tue, 5 Jan 2021 11:31:26
+0100:
> On Tue, Jan 05, 2021 at 11:18:21AM +0100, Felix Fietkau wrote:
> > This reverts stable commit baad618d078c857f99cc286ea249e9629159901f.
> >
> > This commit is adding lines to spinand_write_to_cache_op, wheras the upstream
> > commit 868cbe2a6dcee451bd8f87cbbb2a73cf463b57e5 that this was supposed to
> > backport was touching spinand_read_from_cache_op.
> > It causes a crash on writing OOB data by attempting to write to read-only
> > kernel memory.
> >
> > Cc: Miquel Raynal <miquel.raynal@bootlin.com>
> > Signed-off-by: Felix Fietkau <nbd@nbd.name>
> > ---
> > drivers/mtd/nand/spi/core.c | 4 ----
> > 1 file changed, 4 deletions(-)
>
> So the backport to 5.10.y broke, but not the backport to 4.19.y or
> 5.4.y? Can you provide a "correct" backport for this instead of just
> removing this fix?
Agreed, I think the proper way to handle the situation would be to move
these three lines to spinand_read_from_cache_op() instead of just
getting rid of them.
Thanks,
Miquèl
next prev parent reply other threads:[~2021-01-05 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-05 10:18 [PATCH] Revert "mtd: spinand: Fix OOB read" Felix Fietkau
2021-01-05 10:31 ` Greg KH
2021-01-05 10:40 ` Felix Fietkau
2021-01-05 10:50 ` Greg KH
2021-01-05 10:40 ` Miquel Raynal [this message]
2021-01-05 10:47 ` Felix Fietkau
2021-01-05 11:05 ` 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=20210105114035.2c766901@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=gregkh@linuxfoundation.org \
--cc=nbd@nbd.name \
--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.