All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: juanfengpy@gmail.com
Cc: "Hui Li" <caelli@tencent.com>,
	stable@vger.kernel.org,
	"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>
Subject: Re: [PATCH v7] tty: fix hang on tty device with no_room set
Date: Tue, 4 Apr 2023 09:49:31 +0700	[thread overview]
Message-ID: <ZCuQO3A6FX305KTJ@debian.me> (raw)
In-Reply-To: <1679019847-1401-1-git-send-email-caelli@tencent.com>

[-- Attachment #1: Type: text/plain, Size: 583 bytes --]

On Fri, Mar 17, 2023 at 10:24:07AM +0800, juanfengpy@gmail.com wrote:
> We have met a hang on pty device, the reader was blocking
> at epoll on master side, the writer was sleeping at wait_woken
> inside n_tty_write on slave side, and the write buffer on
> tty_port was full, we found that the reader and writer would
> never be woken again and blocked forever.

Where do you find this hanging pty? Seems like the wording makes me
confused. Maybe you mean "It is possible to hang pty device. In that
case, ..."

-- 
An old man doll... just what I always wanted! - Clara

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-04-04  2:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  2:24 [PATCH v7] tty: fix hang on tty device with no_room set juanfengpy
2023-04-04  2:49 ` Bagas Sanjaya [this message]
2023-04-04  2:55   ` Bagas Sanjaya
2023-04-04  7:02     ` caelli
  -- strict thread matches above, loose matches on Subject: below --
2022-06-27 12:05 [PATCH v5] " Greg KH
2023-03-17  2:37 ` [PATCH v7] " juanfengpy
2023-03-17  2:41 ` juanfengpy
2023-03-17  6:32   ` Jiri Slaby

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=ZCuQO3A6FX305KTJ@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=caelli@tencent.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=juanfengpy@gmail.com \
    --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 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.