From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: minyard@acm.org
Cc: Jiri Slaby <jirislaby@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Peter Hurley <peter@hurleysoftware.com>,
brian.bloniarz@gmail.com
Subject: Re: [PATCH 0/2] drivers:tty:pty: Fix a race causing data loss on close
Date: Thu, 7 Jan 2021 16:32:38 +0100 [thread overview]
Message-ID: <X/cplo+nw5IaG3CJ@kroah.com> (raw)
In-Reply-To: <20201124004902.1398477-1-minyard@acm.org>
On Mon, Nov 23, 2020 at 06:49:00PM -0600, minyard@acm.org wrote:
> I finally got some time to spend with this issue, and I think I have a
> good fix. Not really a v2, this is a completely different fix.
> Basically, calling tty_vhangup() on the slave when closing a pty master
> is just a bad idea.
>
> >From what I can tell, the tty_vhangup() is there in case there was a
> console redirect to the pty slave. When you close the master, you need
> to release the redirect. I didn't see another reason for tty_vhangup().
> So this has two parts, export the release of the tty redirect release
> for the pty code to use, and call it from the pty code.
>
> With this change, everything seems to work ok and no data is lost on the
> slave side if the master closes with outstanding data. I have updated
> my test program to check that all written data is read, it's available
> at https://sourceforge.net/projects/ser2net/files/tmp/testpty.c/download
>
> But, this code is quite intricate and I certainly may have missed
> something.
Tricky stuff, but I think this makes sense, so let's see how the
test-builders and linux-next work with this...
thanks,
greg k-h
prev parent reply other threads:[~2021-01-07 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-24 0:49 minyard
2020-11-24 0:49 ` [PATCH 1/2] tty: Export redirect release minyard
2020-11-24 0:49 ` [PATCH 2/2] drivers:tty:pty: Fix a race causing data loss on close minyard
2021-01-02 14:41 ` Corey Minyard
2021-01-07 15:29 ` Greg Kroah-Hartman
2021-01-07 15:32 ` Greg Kroah-Hartman [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=X/cplo+nw5IaG3CJ@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=brian.bloniarz@gmail.com \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minyard@acm.org \
--cc=peter@hurleysoftware.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®