Linux Serial subsystem development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Hungyu Lin" <dennylin0707@gmail.com>
Cc: linux-serial@vger.kernel.org
Subject: Re: [PATCH v2] tty: discard flip-buffer input for TCSAFLUSH
Date: Tue, 27 Oct 2026 08:32:44 +0000	[thread overview]
Message-ID: <sashiko-outbox-186286@kernel.org> (raw)
In-Reply-To: <20261027082236.56724-1-dennylin0707@gmail.com>

> set_termios() handles TERMIOS_FLUSH by clearing only the line discipline's
> input buffer. Data already committed to the tty flip buffers can be
> delivered after that flush, leaving old input readable after a successful
> tcsetattr(TCSAFLUSH).
> 
> This can be reproduced with a noncanonical PTY: complete an 8192-byte
> master write, wait until the slave reports 4095 unread bytes, and apply
> TCSAFLUSH. The remaining 4097 bytes are still readable afterwards. Small
> amounts of pending input can also survive if they have not reached the
> line discipline yet.
> 
> Use tty_buffer_flush() with the referenced line discipline to discard both
> receive queues under the existing buffer lock. If the line discipline has
> a flush_buffer callback, also unthrottle the tty after releasing that lock,
> as TCIFLUSH does. Otherwise a paused input source or sleeping PTY writer
> can remain stopped after the queues are emptied.
> 
> Signed-off-by: Hungyu Lin <dennylin0707@gmail.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261027082236.56724-1-dennylin0707@gmail.com?part=1


  reply	other threads:[~2026-10-27  8:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27  8:22 [PATCH v2] tty: discard flip-buffer input for TCSAFLUSH Hungyu Lin
2026-10-27  8:32 ` sashiko-bot [this message]
2026-10-27 15:39   ` Hungyu Lin
2026-10-27 19:17 ` Hungyu Lin

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-186286@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=dennylin0707@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox