From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Vinod Koul <vkoul@kernel.org>
Cc: festevam@gmail.com, linux-serial@vger.kernel.org,
gregkh@linuxfoundation.org, s.hauer@pengutronix.de,
linux-kernel@vger.kernel.org,
Chengfeng Ye <dg573847474@gmail.com>,
sorganov@gmail.com, kernel@pengutronix.de,
ilpo.jarvinen@linux.intel.com, dmaengine@vger.kernel.org,
shawnguo@kernel.org, jirislaby@kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND] serial: imx: Fix potential deadlock on sport->port.lock
Date: Thu, 28 Sep 2023 10:44:36 +0200 [thread overview]
Message-ID: <20230928084436.fftw5sk4sixaedck@pengutronix.de> (raw)
In-Reply-To: <ZRUtZ/M3Ml6ltc2m@matsya>
[-- Attachment #1: Type: text/plain, Size: 2037 bytes --]
Hello Vinod,
thanks for your quick answer!
On Thu, Sep 28, 2023 at 01:08:15PM +0530, Vinod Koul wrote:
> On 28-09-23, 08:07, Uwe Kleine-König wrote:
> > [Cc += Vinod Koul, dmaengine@vger.kernel.org]
> >
> > Hello,
> >
> > On Wed, Sep 27, 2023 at 06:19:39PM +0000, Chengfeng Ye wrote:
> > > As &sport->port.lock is acquired under irq context along the following
> > > call chain from imx_uart_rtsint(), other acquisition of the same lock
> > > inside process context or softirq context should disable irq avoid double
> > > lock.
> > >
> > > <deadlock #1>
> > >
> > > imx_uart_dma_rx_callback()
> > > --> spin_lock(&sport->port.lock)
> > > <interrupt>
> > > --> imx_uart_rtsint()
> > > --> spin_lock(&sport->port.lock)
> > >
> > > This flaw was found by an experimental static analysis tool I am
> > > developing for irq-related deadlock.
> >
> > Ah, I understood before that you really experienced that deadlock (or a
> > lockdep splat). I didn't test anything, but I think the
> > imx_uart_dma_rx_callback() is called indirectly by
> > sdma_update_channel_loop() which is called in irq context. I don't know
> > if this is the case for all dma drivers?!
> >
> > @Vinod: Maybe you can chime in here: Is a dma callback always called in
> > irq context?
>
> Not in callback but a tasklet context. The DMA irq handler is supposed
> to use a tasklet for invoking the callback
So drivers/dma/imx-sdma.c is bogous as it calls
-> sdma_int_handler()
-> sdma_update_channel_loop()
-> dmaengine_desc_get_callback_invoke()
resulting in imx_uart_dma_rx_callback() (and others) being called in irq
context, right?
In that case:
Acked-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de>
(for the imx-UART patch that stops assuming imx_uart_dma_rx_callback()
is called with irqs off).
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | https://www.pengutronix.de/ |
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2023-09-28 8:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 18:19 [PATCH RESEND] serial: imx: Fix potential deadlock on sport->port.lock Chengfeng Ye
2023-09-28 6:07 ` Uwe Kleine-König
2023-09-28 7:38 ` Vinod Koul
2023-09-28 8:44 ` Uwe Kleine-König [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=20230928084436.fftw5sk4sixaedck@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=dg573847474@gmail.com \
--cc=dmaengine@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=sorganov@gmail.com \
--cc=vkoul@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