All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "James Hilliard" <james.hilliard1@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v11 5/8] serial: core: allow drivers to reserve flushed transmit storage
Date: Tue, 10 Nov 2026 04:24:03 +0000	[thread overview]
Message-ID: <sashiko-outbox-206190@kernel.org> (raw)
In-Reply-To: <20261109-submit-serial-8250-dma-cancel-v1-v11-5-6364edca63d6@gmail.com>

> uart_flush_buffer() resets the transmit FIFO before calling the driver's
> flush callback. An asynchronous DMA transfer can still access that storage
> after the callback returns, while a new write can immediately reuse it.
> 
> Add uart_xmit_block() and uart_xmit_unblock() so a driver can reserve the
> flushed storage until its transfer and completion callbacks have retired.
> Serialize the reservation with FIFO producers using the port lock.
> 
> While the storage is reserved, write_room() reports no space and write()
> and put_char() accept no data. Defer write-ready notifications until the
> reservation is released, preserving one-shot TTY wakeups. Keep the flush's
> write-ready notification under the port lock so it cannot race another
> reservation.
> 
> Wake tty->write_wait after flushing even when writes remain blocked.
> [ ... ]
> Assert the port-lock requirement at uart_write_wakeup(), alongside the
> reservation helpers, so callers cannot inspect readiness or release a
> one-shot notification concurrently with a reservation change.
> 
> Signed-off-by: James Hilliard <james.hilliard1@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261109-submit-serial-8250-dma-cancel-v1-v11-0-6364edca63d6@gmail.com?part=5


  reply	other threads:[~2026-11-10  4:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-10  4:00 [PATCH v11 0/8] serial: 8250: serialize DMA cancellation with buffer reuse James Hilliard
2026-11-10  4:00 ` [PATCH v11 1/8] serial: 8250_omap: separate locked TX DMA completion processing James Hilliard
2026-11-10  4:05   ` sashiko-bot
2026-11-10  4:00 ` [PATCH v11 2/8] serial: serialize asynchronous write wakeups with the port lock James Hilliard
2026-11-10  4:15   ` sashiko-bot
2026-11-10  4:00 ` [PATCH v11 3/8] serial: 8250_omap: serialize RX DMA completion and flushing James Hilliard
2026-11-10  4:10   ` sashiko-bot
2026-11-10  4:00 ` [PATCH v11 4/8] serial: 8250_omap: quiesce DMA IRQ handling before shutdown James Hilliard
2026-11-10  4:29   ` sashiko-bot
2026-11-10  4:00 ` [PATCH v11 5/8] serial: core: allow drivers to reserve flushed transmit storage James Hilliard
2026-11-10  4:24   ` sashiko-bot [this message]
2026-11-10  4:00 ` [PATCH v11 6/8] serial: 8250: drain canceled TX DMA before reusing its buffer James Hilliard
2026-11-10  4:29   ` sashiko-bot
2026-11-10  4:00 ` [PATCH v11 7/8] serial: 8250: retire canceled RX DMA before reusing the receive buffer James Hilliard
2026-11-10  4:41   ` sashiko-bot
2026-11-10 21:05   ` Raul E Rangel
2026-11-10  4:00 ` [PATCH v11 8/8] serial: 8250: retain DMA resources when termination fails James Hilliard
2026-11-10  4:35   ` sashiko-bot

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=sashiko-outbox-206190@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=james.hilliard1@gmail.com \
    --cc=linux-serial@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.