From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Simon Arlott <simon@octiron.net>
Cc: <linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<linux-can@vger.kernel.org>,
Marc Kleine-Budde <mkl@pengutronix.de>,
"Vincent Mailhol" <mailhol.vincent@wanadoo.fr>
Subject: Re: [PATCH] can: mcp251x: fix deadlock if an interrupt occurs during mcp251x_open
Date: Mon, 19 Aug 2024 14:00:29 +0200 [thread overview]
Message-ID: <0c45e6aa-3712-431a-8198-eb87d04a7cab@intel.com> (raw)
In-Reply-To: <ea44fb76-0a9d-4009-8eba-021f0928cc77@0882a8b5-c6c3-11e9-b005-00805fc181fe.uuid.home.arpa>
On 8/17/24 17:45, Simon Arlott wrote:
> The mcp251x_hw_wake() function is called with the mpc_lock mutex held and
> disables the interrupt handler so that no interrupts can be processed while
> waking the device. If an interrupt has already occurred then waiting for
> the interrupt handler to complete will deadlock because it will be trying
> to acquire the same mutex.
>
> CPU0 CPU1
> ---- ----
> mcp251x_open()
> mutex_lock(&priv->mcp_lock)
> request_threaded_irq()
> <interrupt>
> mcp251x_can_ist()
> mutex_lock(&priv->mcp_lock)
> mcp251x_hw_wake()
> disable_irq() <-- deadlock
>
> Use disable_irq_nosync() instead because the interrupt handler does
> everything while holding the mutex so it doesn't matter if it's still
> running.
>
> Signed-off-by: Simon Arlott <simon@octiron.net>
You have to provide a Fixes: tag for bugfixes [PATCH net]
otherwise the change looks fine for me,
Reviewed-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> ---
> drivers/net/can/spi/mcp251x.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/can/spi/mcp251x.c b/drivers/net/can/spi/mcp251x.c
> index 3b8736ff0345..ec5c64006a16 100644
> --- a/drivers/net/can/spi/mcp251x.c
> +++ b/drivers/net/can/spi/mcp251x.c
> @@ -752,7 +752,7 @@ static int mcp251x_hw_wake(struct spi_device *spi)
> int ret;
>
> /* Force wakeup interrupt to wake device, but don't execute IST */
> - disable_irq(spi->irq);
> + disable_irq_nosync(spi->irq);
> mcp251x_write_2regs(spi, CANINTE, CANINTE_WAKIE, CANINTF_WAKIF);
>
> /* Wait for oscillator startup timer after wake up */
prev parent reply other threads:[~2024-08-19 12:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-17 15:45 Simon Arlott
2024-08-19 12:00 ` Przemek Kitszel [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=0c45e6aa-3712-431a-8198-eb87d04a7cab@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=simon@octiron.net \
/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
all inboxes | Powered by JetHome®