From: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: "linux-serial@vger.kernel.org" <linux-serial@vger.kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Heikki Krogerus <heikki.krogerus@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: RE: [PATCH 2/2] serial: 8250: Fix serial8250_tx_empty() race with DMA Tx
Date: Fri, 17 Mar 2023 12:51:35 +0200 (EET) [thread overview]
Message-ID: <ce143371-3ad-6c8-a37c-f8bcbc9382a@linux.intel.com> (raw)
In-Reply-To: <55704d488ee644f5a710841f3912b25f@AcuMS.aculab.com>
[-- Attachment #1: Type: text/plain, Size: 2689 bytes --]
On Fri, 17 Mar 2023, David Laight wrote:
> From: Ilpo Järvinen
> > Sent: 16 March 2023 13:25
> >
> > There's a potential race before THRE/TEMT deasserts when DMA Tx is
> > starting up (or the next batch of continuous Tx is being submitted).
> > This can lead to misdetecting Tx empty condition.
> >
> > It is entirely normal for THRE/TEMT to be set for some time after the
> > DMA Tx had been setup in serial8250_tx_dma(). As Tx side is definitely
> > not empty at that point, it seems incorrect for serial8250_tx_empty()
> > claim Tx is empty.
> >
> > Fix the race by also checking in serial8250_tx_empty() whether there's
> > DMA Tx active.
> >
> > Note: This fix only addresses in-kernel race mainly to make using
> > TCSADRAIN/FLUSH robust. Userspace can still cause other races but they
> > seem userspace concurrency control problems.
> >
> > Fixes: 9ee4b83e51f74 ("serial: 8250: Add support for dmaengine")
> > Cc: stable@vger.kernel.org
> > Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
> > ---
> > drivers/tty/serial/8250/8250.h | 12 ++++++++++++
> > drivers/tty/serial/8250/8250_port.c | 7 ++++++-
> > 2 files changed, 18 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/tty/serial/8250/8250.h b/drivers/tty/serial/8250/8250.h
> ...
> > static inline int ns16550a_goto_highspeed(struct uart_8250_port *up)
> > diff --git a/drivers/tty/serial/8250/8250_port.c b/drivers/tty/serial/8250/8250_port.c
> > index fa43df05342b..4954c4f15fb2 100644
> > --- a/drivers/tty/serial/8250/8250_port.c
> > +++ b/drivers/tty/serial/8250/8250_port.c
> > @@ -2006,17 +2006,22 @@ static unsigned int serial8250_tx_empty(struct uart_port *port)
> > {
> > struct uart_8250_port *up = up_to_u8250p(port);
> > unsigned long flags;
> > + bool dma_tx_running;
> > u16 lsr;
> >
> > serial8250_rpm_get(up);
> >
> > spin_lock_irqsave(&port->lock, flags);
> > lsr = serial_lsr_in(up);
> > + dma_tx_running = serial8250_tx_dma_running(up);
> > spin_unlock_irqrestore(&port->lock, flags);
> >
> > serial8250_rpm_put(up);
> >
> > - return uart_lsr_tx_empty(lsr) ? TIOCSER_TEMT : 0;
> > + if (uart_lsr_tx_empty(lsr) && !dma_tx_running)
> > + return TIOCSER_TEMT;
> > +
> > + return 0;
> > }
>
> Since checking whether dma is active is fast but reading
> the lsr is slow it is probably better to generate the return
> value inside the lock and test for dma first.
> Something like:
> spin_lock()
> result = 0;
> if (!serial8250_tx_dma_running(up) &&
> uart_lsr_tx_empty(serial_lsr_in(up)))
> result = TIOCSER_TEMT;
> }
> spin_unlock()
> ...
> return result;
>
> David
Thanks, I'll change it to something along those lines.
--
i.
prev parent reply other threads:[~2023-03-17 10:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 13:24 [PATCH 0/2] tty/serial: Fix tcsetattr() TCSADRAIN/FLUSH and write() races Ilpo Järvinen
2023-03-16 13:24 ` [PATCH 1/2] tty: Prevent writing chars during tcsetattr TCSADRAIN/FLUSH Ilpo Järvinen
2023-03-16 13:24 ` [PATCH 2/2] serial: 8250: Fix serial8250_tx_empty() race with DMA Tx Ilpo Järvinen
2023-03-17 8:09 ` David Laight
2023-03-17 10:51 ` Ilpo Järvinen [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=ce143371-3ad-6c8-a37c-f8bcbc9382a@linux.intel.com \
--to=ilpo.jarvinen@linux.intel.com \
--cc=David.Laight@ACULAB.COM \
--cc=gregkh@linuxfoundation.org \
--cc=heikki.krogerus@linux.intel.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--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
all inboxes | Powered by JetHome®