From: Lukas Wunner <lukas@wunner.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-spi@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Vladimir Oltean <olteanv@gmail.com>,
Daniel Mack <daniel@zonque.org>,
kernel@pengutronix.de
Subject: Re: [PATCH 0/6] Fix use-after-free in SPI drivers
Date: Thu, 15 Oct 2020 07:44:23 +0200 [thread overview]
Message-ID: <20201015054423.GA21422@wunner.de> (raw)
In-Reply-To: <20200922093228.24917-1-s.hauer@pengutronix.de>
On Tue, Sep 22, 2020 at 11:32:22AM +0200, Sascha Hauer wrote:
> spi: bcm2835: Use devm_spi_register_controller()
> spi: dw: Use devm_spi_register_controller()
> spi: pxa2xx: Use devm_spi_register_controller()
Sorry but NAK at least for these three patches as they re-introduce
the issue fixed by 9dd277ff92d0, 32e5b57232c0, ca8b19d61e3f.
The use-after-free is real but it needs to be addressed differently.
Let's continue the discussion in this thread:
https://lore.kernel.org/linux-spi/20201015053829.GA2461@wunner.de/
Thanks,
Lukas
prev parent reply other threads:[~2020-10-15 5:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 9:32 [PATCH 0/6] Fix use-after-free in SPI drivers Sascha Hauer
2020-09-22 9:32 ` [PATCH 1/6] spi: fsl-dspi: Use devm_spi_register_controller() Sascha Hauer
2020-09-22 9:44 ` Mark Brown
2020-09-22 11:06 ` Sascha Hauer
2020-09-22 11:25 ` Mark Brown
2020-09-22 9:32 ` [PATCH 2/6] spi: atmel-quadspi: " Sascha Hauer
2020-09-22 9:32 ` [PATCH 3/6] spi: bcm2835: " Sascha Hauer
2020-09-22 9:39 ` Nicolas Saenz Julienne
2020-09-22 9:32 ` [PATCH 4/6] spi: dw: " Sascha Hauer
2020-09-22 9:32 ` [PATCH 5/6] spi: pxa2xx: " Sascha Hauer
2020-09-22 9:32 ` [PATCH 6/6] spi: rpc-if: " Sascha Hauer
2020-10-15 5:44 ` Lukas Wunner [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=20201015054423.GA21422@wunner.de \
--to=lukas@wunner.de \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=kernel@pengutronix.de \
--cc=linux-spi@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=nsaenzjulienne@suse.de \
--cc=olteanv@gmail.com \
--cc=s.hauer@pengutronix.de \
/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).