All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: Richard Genoud <richard.genoud@gmail.com>
Cc: Jiri Slaby <jslaby@suse.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: stty blocks forever when the line is already opened (and the tx buffer can't be flushed)
Date: Wed, 27 Jan 2016 15:33:36 -0800	[thread overview]
Message-ID: <56A953D0.4070600@hurleysoftware.com> (raw)
In-Reply-To: <CACQ1gAhUJGdgfB4oape9W4-0bgyLhW1AhySSvQtM8A+kv8cASQ@mail.gmail.com>

On 01/27/2016 02:26 AM, Richard Genoud wrote:
> 2016-01-27 10:14 GMT+01:00 Richard Genoud <richard.genoud@gmail.com>:
>> 2016-01-26 18:13 GMT+01:00 Peter Hurley <peter@hurleysoftware.com>:
>>> Hi Richard,
>>>
>>> On 01/26/2016 08:19 AM, Richard Genoud wrote:
>>>> [ sorry for the noise, I forgot to Cc the lkml ]
>>>>
>>>> Hi,
>>>> I've found a case were calling
>>>> stty -F /dev/ttyS1 clocal
>>>> blocks forever.
>>>> And I don't know if it's a very old bug or if it's meant to be like that.
>>>>
>>>> Here is how to reproduce the lock :
>>>> NB: there's NO modem on ttyS1
>>>> stty -F /dev/ttyS1 clocal cread crtscts
>>>> cat < /dev/ttyS1
>>>>
>>>> #on another terminal :
>>>> echo "dummy" > /dev/ttyS1  # This call doesn't block
>>>>
>>>> stty -F /dev/ttyS1 -crtscts # this blocks forever on ioctl(TCSETSW )
>>>>
>>>>
>>>> looking at tty_port_close_start(), it's pretty clear that nothing is
>>>> flushed until the last user, so it explains why the "echo dummy"
>>>> returns directly, despite the crtscts flags.
>>>> And in tty_mode_ioctl(), there are the lines:
>>>>         case TCSETSW:
>>>>                 return set_termios(real_tty, p, TERMIOS_WAIT | TERMIOS_OLD);
>>>> That explain why the stty blocks.
>>>>
>>>> But this behavior seems really strange.
>>>> ... Or it's meant to be like that ?
>>>
>>> Yeah, meant to be like that.
>>>
>>> When mgetty writes the login prompt but h/w flow control is enabled
>>> and nothing's connected, the output is buffered.
>>>
>>> Since stty uses tcsetattr(TCSADRAIN), the attempt to turn off h/w flow
>>> control blocks, waiting for output to empty.
>> Damn ! I forgot about the TCSADRAIN/FLUSH/NOW flags
>>
>>> In this situation, stopping mgetty will allow the other process
>>> to unblock and advance.
>>>
>>> Hmmm, I could add a -f,--force flag to stty so it uses tcsetattr(TCSANOW)...
>> Yes, I think such a flag will make sense.
> In fact, a similar flag exist in the very last version of coreutils (8.25)
> http://git.savannah.gnu.org/cgit/coreutils.git/commit/?id=cb7d8b90a213c0186a8c8ba66da959e1f5930e78
> :)
> 

Thanks for saving me the time doing it myself.

Regards,
Peter Hurley

      reply	other threads:[~2016-01-27 23:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CACQ1gAjNSTyXLVXp7zrdda2eFfA=aQ4tp_PAMRK+Syh-Va8zaw@mail.gmail.com>
2016-01-26 16:19 ` stty blocks forever when the line is already opened (and the tx buffer can't be flushed) Richard Genoud
2016-01-26 17:13   ` Peter Hurley
2016-01-27  9:14     ` Richard Genoud
2016-01-27 10:26       ` Richard Genoud
2016-01-27 23:33         ` Peter Hurley [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=56A953D0.4070600@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.genoud@gmail.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 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.