From: Sergey Shtylyov <s.shtylyov@omprussia.ru>
To: Lukas Wunner <lukas@wunner.de>, Mark Brown <broonie@kernel.org>
Cc: <linux-spi@vger.kernel.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH for-5.10] spi: rpc-if: Fix use-after-free on unbind
Date: Sat, 28 Nov 2020 23:20:50 +0300 [thread overview]
Message-ID: <9534f4fb-6f5e-b538-6903-e702a7301b1d@omprussia.ru> (raw)
In-Reply-To: <bf610a9fc88376e2cdf661c4ad0bb275ee5f4f20.1605512876.git.lukas@wunner.de>
Hello!
On 11/16/20 11:23 AM, Lukas Wunner wrote:
> rpcif_spi_remove() accesses the driver's private data after calling
> spi_unregister_controller() even though that function releases the last
> reference on the spi_controller and thereby frees the private data.
OK, your analysis seems correct (sorry for the delay admitting this :-).
Not sure why spi_unregister_controller() drops the device reference while
spi_register_controller() itself doesn't allocate the memory...
> Fix by switching over to the new devm_spi_alloc_master() helper which
> keeps the private data accessible until the driver has unbound.
Perhaps the order of the calls in the remove() method could be reversed?
> Fixes: eb8d6d464a27 ("spi: add Renesas RPC-IF driver")
> Signed-off-by: Lukas Wunner <lukas@wunner.de>
> Cc: <stable@vger.kernel.org> # v5.9+: 5e844cc37a5c: spi: Introduce device-managed SPI controller allocation
> Cc: <stable@vger.kernel.org> # v5.9+
> Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
[...]
MBR, Sergei
next prev parent reply other threads:[~2020-11-28 22:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 8:23 [PATCH for-5.10] spi: spi-geni-qcom: Fix use-after-free on unbind Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-qcom-qspi: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-sh: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: pxa2xx: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: rpc-if: " Lukas Wunner
2020-11-28 20:20 ` Sergey Shtylyov [this message]
2020-11-29 11:35 ` Lukas Wunner
2020-11-30 19:18 ` Sergey Shtylyov
2020-12-02 11:43 ` Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: mxic: Don't leak SPI master in probe error path Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: mt7621: " Lukas Wunner
2020-11-16 11:05 ` Stefan Roese
2020-11-16 8:23 ` [PATCH for-5.10] spi: spi-mtk-nor: " Lukas Wunner
2020-11-17 4:02 ` Ikjoon Jang
2020-11-17 12:32 ` Mark Brown
2020-11-16 8:23 ` [PATCH for-5.10] spi: gpio: " Lukas Wunner
2020-11-16 19:23 ` Andrey Smirnov
2020-11-16 23:03 ` Lukas Wunner
2020-11-16 23:59 ` Andrey Smirnov
2020-11-18 1:08 ` Linus Walleij
2020-11-16 8:23 ` [PATCH for-5.10] spi: npcm-fiu: " Lukas Wunner
2020-11-17 22:38 ` Mark Brown
2020-12-01 13:57 ` Mark Brown
2020-12-01 14:30 ` Lukas Wunner
2020-12-01 17:17 ` Mark Brown
2020-12-01 17:49 ` Lukas Wunner
2020-12-02 15:17 ` Mark Brown
2020-11-16 8:23 ` [PATCH for-5.10] spi: rb4xx: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] spi: sc18is602: " Lukas Wunner
2020-11-16 8:23 ` [PATCH for-5.10] media: netup_unidvb: " Lukas Wunner
2020-11-23 14:06 ` Mauro Carvalho Chehab
2020-12-01 13:57 ` Mark Brown
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=9534f4fb-6f5e-b538-6903-e702a7301b1d@omprussia.ru \
--to=s.shtylyov@omprussia.ru \
--cc=broonie@kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=sergei.shtylyov@cogentembedded.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).