public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@suse.de>
To: linux-kernel@vger.kernel.org
Subject: Pty is losing bytes
Date: Tue, 15 Feb 2005 01:54:25 +0100	[thread overview]
Message-ID: <jebramy75q.fsf@sykes.suse.de> (raw)

Recent kernel are losing bytes on a pty.  Try running this program (needs
to be linked against -lutil) with a moderately large input (10K - 20K).
The output should match its input, but instead there is always one byte
missing at the end of the first 4K chunk read by the child.

#include <stdlib.h>
#include <string.h>
#include <unistd.h>
#include <pty.h>
#include <sys/wait.h>

char buf[4096];

int main (void)
{
    int master;
    int stdout = dup (1);
    int pid = forkpty (&master, 0, 0, 0);
    int bytes_read;
    int bytes_written;

    if (pid < 0) exit (1);
    if (pid > 0) {
        while ((bytes_read = read (0, buf, sizeof (buf))) > 0) {
            char *p = buf;
            while (bytes_read > 0 &&
                   (bytes_written = write (master, p, bytes_read)) > 0)
              bytes_read -= bytes_written, p += bytes_written;
        }
        write (master, "EOF\n", 4);
        waitpid (pid, 0, 0);
        exit (0);
    }

    while ((bytes_read = read (0, buf, sizeof (buf))) > 0) {
        char *p = buf;
        if (strncmp (buf, "EOF\n", 4) == 0) break;
        while (bytes_read > 0 &&
               (bytes_written = write (stdout, p, bytes_read)) > 0)
          bytes_read -= bytes_written, p += bytes_written;
    }
    exit (0);
}

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

             reply	other threads:[~2005-02-15  0:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-15  0:54 Andreas Schwab [this message]
2005-02-15 19:08 ` Pty is losing bytes Linus Torvalds
2005-02-15 19:44   ` Linus Torvalds
2005-02-15 22:13     ` Alan Cox
2005-02-15 19:58   ` Sergey Vlasov
2005-02-15 20:13     ` Sergey Vlasov
2005-02-15 20:06   ` Alan Curry
2005-02-15 20:30   ` Andreas Schwab
2005-02-15 20:56     ` Linus Torvalds
2005-02-15 21:54       ` Andreas Schwab
2005-02-16  3:12       ` Roman Zippel
2005-02-16  4:05         ` Linus Torvalds
2005-02-16 14:42           ` Theodore Ts'o
2005-02-16 16:06             ` Linus Torvalds
2005-02-17  4:44               ` Theodore Ts'o
2005-02-17 15:45                 ` Linus Torvalds
2005-02-18 16:32                   ` Theodore Ts'o
2005-02-16 19:49           ` Roman Zippel
2005-02-16 19:58             ` Linus Torvalds
2005-02-16 22:46               ` Andrew Morton
  -- strict thread matches above, loose matches on Subject: below --
2005-02-15  2:00 Alex Davis
2005-02-15 10:48 ` Andreas Schwab
2005-02-15 11:01   ` Jan De Luyck

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=jebramy75q.fsf@sykes.suse.de \
    --to=schwab@suse.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox