From: Greg KH <gregkh@linuxfoundation.org>
To: "Ömer Mete Kaya" <omermetekaya0@gmail.com>
Cc: jirislaby@kernel.org, linux-kernel@vger.kernel.org,
linux-serial@vger.kernel.org,
syzbot+d84934b4184d7f9a1aed@syzkaller.appspotmail.com
Subject: Re: [PATCH] tty: fix lock order inversion in tty_buffer_flush()
Date: Wed, 23 Sep 2026 14:56:07 +0200 [thread overview]
Message-ID: <2026092316-treadmill-disparity-8a38@gregkh> (raw)
In-Reply-To: <20260804140251.8197-1-omermetekaya0@gmail.com>
On Tue, Aug 04, 2026 at 05:02:51PM +0300, Ömer Mete Kaya wrote:
> tty_buffer_flush() calls ld->ops->flush_buffer() while holding
> buf->lock. For the N_TTY line discipline, flush_buffer() is
> n_tty_flush_buffer(), which acquires termios_rwsem.
>
> However, the documented stable lock order (see tty.h) is:
> termios_rwsem -> buf->lock
>
> Calling flush_buffer() under buf->lock inverts this order and creates
> a circular locking dependency detected by lockdep:
>
> &buf->lock -> console_lock -> &port->mutex -> &tty->termios_rwsem
> -> &buf->lock
>
> Fix this by moving the flush_buffer() call outside buf->lock.
> The buffer data has already been discarded at this point, so the
> ordering change is safe.
>
> Reported-by: syzbot+d84934b4184d7f9a1aed@syzkaller.appspotmail.com
> Closes: https://syzkaller.appspot.com/bug?extid=d84934b4184d7f9a1aed
Did syzbot actually test this? How did you test this?
Did you forget an Assisted-by: tag?
> Signed-off-by: Ömer Mete Kaya <omermetekaya0@gmail.com>
> ---
> drivers/tty/tty_buffer.c | 10 +++++++---
> 1 file changed, 7 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/tty/tty_buffer.c b/drivers/tty/tty_buffer.c
> index 96be90db5..bb7b7fbcb 100644
> --- a/drivers/tty/tty_buffer.c
> +++ b/drivers/tty/tty_buffer.c
> @@ -244,11 +244,15 @@ void tty_buffer_flush(struct tty_struct *tty, struct tty_ldisc *ld)
> buf->head->read = buf->head->commit;
> buf->head->lookahead = buf->head->read;
>
> - if (ld && ld->ops->flush_buffer)
> - ld->ops->flush_buffer(tty);
> -
> atomic_dec(&buf->priority);
> mutex_unlock(&buf->lock);
> + /*
> + * Call flush_buffer() outside buf->lock: n_tty_flush_buffer()
> + * acquires termios_rwsem, but the required lock order is
> + * termios_rwsem -> buf->lock, not the other way around.
> + */
> + if (ld && ld->ops->flush_buffer)
> + ld->ops->flush_buffer(tty);
This feels wrong, what is going to break with this change? What commit
does this change fix?
thanks,
greg k-h
prev parent reply other threads:[~2026-09-23 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 14:02 Ömer Mete Kaya
2026-09-23 12:56 ` Greg KH [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=2026092316-treadmill-disparity-8a38@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=omermetekaya0@gmail.com \
--cc=syzbot+d84934b4184d7f9a1aed@syzkaller.appspotmail.com \
/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®