From: Andreas Schwab <schwab@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-serial@vger.kernel.org
Subject: Re: Don't cross the (tty) streams
Date: Thu, 20 Sep 2007 23:29:31 +0200 [thread overview]
Message-ID: <jer6ktt490.fsf@sykes.suse.de> (raw)
In-Reply-To: <20070920210221.GC10625@parisc-linux.org> (Matthew Wilcox's message of "Thu\, 20 Sep 2007 15\:02\:22 -0600")
Matthew Wilcox <matthew@wil.cx> writes:
> Connect two machines with a serial cable. On the victim:
>
> willy@rowlf:~$ cat </dev/ttyS1
>
> Now, let's find out which ttyS on the other machine is connected ...
>
> willy@teeth:~$ echo foo >/dev/ttyS1
> -bash: echo: write error: Input/output error
>
> Oops, that's not a serial port. No output on rowlf, as expected.
> OK, carrying on ...
>
> willy@teeth:~$ echo bar >/dev/ttyS0
>
> And yet on rowlf, we now see:
>
> foo
> bar
>
> Looks like there's an error path that doesn't throw away data on -EIO.
Read the thread starting here:
<http://lists.gnu.org/archive/html/bug-bash/2007-09/msg00020.html>.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
-
To unsubscribe from this list: send the line "unsubscribe linux-serial" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Andreas Schwab <schwab@suse.de>
To: Matthew Wilcox <matthew@wil.cx>
Cc: linux-kernel@vger.kernel.org, Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-serial@vger.kernel.org
Subject: Re: Don't cross the (tty) streams
Date: Thu, 20 Sep 2007 23:29:31 +0200 [thread overview]
Message-ID: <jer6ktt490.fsf@sykes.suse.de> (raw)
In-Reply-To: <20070920210221.GC10625@parisc-linux.org> (Matthew Wilcox's message of "Thu\, 20 Sep 2007 15\:02\:22 -0600")
Matthew Wilcox <matthew@wil.cx> writes:
> Connect two machines with a serial cable. On the victim:
>
> willy@rowlf:~$ cat </dev/ttyS1
>
> Now, let's find out which ttyS on the other machine is connected ...
>
> willy@teeth:~$ echo foo >/dev/ttyS1
> -bash: echo: write error: Input/output error
>
> Oops, that's not a serial port. No output on rowlf, as expected.
> OK, carrying on ...
>
> willy@teeth:~$ echo bar >/dev/ttyS0
>
> And yet on rowlf, we now see:
>
> foo
> bar
>
> Looks like there's an error path that doesn't throw away data on -EIO.
Read the thread starting here:
<http://lists.gnu.org/archive/html/bug-bash/2007-09/msg00020.html>.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2007-09-20 21:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-20 21:02 Don't cross the (tty) streams Matthew Wilcox
2007-09-20 21:29 ` Andreas Schwab [this message]
2007-09-20 21:29 ` Andreas Schwab
2007-09-21 3:08 ` Matthew Wilcox
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=jer6ktt490.fsf@sykes.suse.de \
--to=schwab@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthew@wil.cx \
/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.