public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: linux-kernel@vger.kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.cz>
Subject: Re: Strange intermittent EIO error when writing to stdout since v3.8.0
Date: Sat, 08 Jun 2013 13:56:01 -0500	[thread overview]
Message-ID: <1370717761.2776.84@driftwood> (raw)
In-Reply-To: <20130606115417.GA520@x4> (from markus@trippelsdorf.de on Thu Jun  6 06:54:17 2013)

On 06/06/2013 06:54:17 AM, Markus Trippelsdorf wrote:
> Since v3.8.0 several people reported intermittent IO errors that  
> happen
> during high system load while using "emerge" under Gentoo:
...
> see: https://bugs.gentoo.org/show_bug.cgi?id=459674
> 
> (A similar issue also happens when building Firefox since v3.8.0. But
> because Firefox's build process doesn't raise an exception it just  
> dies
> at random points without giving a clue.)
> 
> Now the question is: Could this be a kernel bug? Maybe in the TTY  
> layer?
> 
> Unfortunately the issue is not easily reproducible and a git-bisect is
> out of the question.

I tracked down and fixed something like this in the User Mode Linux tty  
implementation many moons ago.

The trick to making it reproducible was to rename a copy of the xterm  
binary to somethingunique, run a shell in said xterm (because "cat"  
doesn't exercise the tty logic, that's why), run a thing in there  
producing test output, and have a loop in another window doing "while  
true; do killall -STOP somethingunique; sleep 1; killall -START  
somethingunique; sleep 1; done".

This forces the pipe buffer to the pty to fill up and exercise the flow  
control logic, plus all the fun "short write and retry" stuff...

Rob

      parent reply	other threads:[~2013-06-09  1:59 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06 11:54 Strange intermittent EIO error when writing to stdout since v3.8.0 Markus Trippelsdorf
2013-06-06 14:18 ` Peter Hurley
2013-06-06 14:37   ` Markus Trippelsdorf
2013-06-07 15:39     ` Peter Hurley
2013-06-07 16:07       ` Markus Trippelsdorf
2013-06-07 18:22       ` Mikael Pettersson
2013-06-13 10:39         ` Markus Trippelsdorf
2013-06-13 14:16           ` Peter Hurley
2013-06-13 14:51             ` Markus Trippelsdorf
2013-06-13 15:25               ` [PATCH] tty: Debug EIO from write() Peter Hurley
2013-06-13 16:16                 ` Markus Trippelsdorf
2013-06-13 16:29                   ` Peter Hurley
2013-06-13 19:56                     ` [PATCH] tty: Fix transient pty write() EIO Peter Hurley
2013-06-16 17:31                       ` Mikael Pettersson
2013-06-07 19:56       ` Strange intermittent EIO error when writing to stdout since v3.8.0 David Howells
2013-06-11 22:14       ` Orion Poplawski
2013-06-13 10:38         ` Markus Trippelsdorf
2013-06-06 14:41 ` Mikael Pettersson
2013-06-06 17:31 ` David Howells
2013-06-06 18:41   ` Markus Trippelsdorf
2013-06-08 18:56 ` Rob Landley [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=1370717761.2776.84@driftwood \
    --to=rob@landley.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markus@trippelsdorf.de \
    /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