From: Sasha Levin <sashal@kernel.org>
To: gregkh@linuxfoundation.org
Cc: lukas@wunner.de, broonie@kernel.org, linus.walleij@linaro.org,
stable@vger.kernel.org
Subject: Re: FAILED: patch "[PATCH] spi: Fix controller unregister order" failed to apply to 4.19-stable tree
Date: Mon, 15 Jun 2020 19:40:46 -0400 [thread overview]
Message-ID: <20200615234046.GG1931@sasha-vm> (raw)
In-Reply-To: <159223444415976@kroah.com>
On Mon, Jun 15, 2020 at 05:20:44PM +0200, gregkh@linuxfoundation.org wrote:
>
>The patch below does not apply to the 4.19-stable tree.
>If someone wants it applied there, or to any other stable or longterm
>tree, then please email the backport, including the original git commit
>id to <stable@vger.kernel.org>.
>
>thanks,
>
>greg k-h
>
>------------------ original commit in Linus's tree ------------------
>
>From 84855678add8aba927faf76bc2f130a40f94b6f7 Mon Sep 17 00:00:00 2001
>From: Lukas Wunner <lukas@wunner.de>
>Date: Fri, 15 May 2020 17:58:01 +0200
>Subject: [PATCH] spi: Fix controller unregister order
>
>When an SPI controller unregisters, it unbinds all its slave devices.
>For this, their drivers may need to access the SPI bus, e.g. to quiesce
>interrupts.
>
>However since commit ffbbdd21329f ("spi: create a message queueing
>infrastructure"), spi_destroy_queue() is executed before unbinding the
>slaves. It sets ctlr->running = false, thereby preventing SPI bus
>access and causing unbinding of slave devices to fail.
>
>Fix by unbinding slaves before calling spi_destroy_queue().
>
>Fixes: ffbbdd21329f ("spi: create a message queueing infrastructure")
>Signed-off-by: Lukas Wunner <lukas@wunner.de>
>Cc: stable@vger.kernel.org # v3.4+
>Cc: Linus Walleij <linus.walleij@linaro.org>
>Link: https://lore.kernel.org/r/8aaf9d44c153fe233b17bc2dec4eb679898d7e7b.1589557526.git.lukas@wunner.de
>Signed-off-by: Mark Brown <broonie@kernel.org>
I've also grabbed:
ebc37af5e0a1 ("spi: No need to assign dummy value in spi_unregister_controller()")
And again worked around not having:
8caab75fd2c2 ("spi: Generalize SPI "master" to "controller"")
And queued these two patches for 4.19, 4.14, 4.9, and 4.4.
--
Thanks,
Sasha
prev parent reply other threads:[~2020-06-15 23:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 15:20 FAILED: patch "[PATCH] spi: Fix controller unregister order" failed to apply to 4.19-stable tree gregkh
2020-06-15 23:40 ` Sasha Levin [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=20200615234046.GG1931@sasha-vm \
--to=sashal@kernel.org \
--cc=broonie@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=lukas@wunner.de \
--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 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).