From: simon@nuit.ca
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Cannot access '/dev/pts/292': Value too large for defined data type
Date: Sat, 26 Jun 2004 23:21:06 +0000 [thread overview]
Message-ID: <20040626232104.GA32365@nuit.ca> (raw)
In-Reply-To: <20040626135948.7b4396e9.akpm@osdl.org>
[-- Attachment #1: Type: text/plain, Size: 1137 bytes --]
Ce jour Sat, 26 Jun 2004, Andrew Morton a dit:
> simon@nuit.ca wrote:
> >
> > whenever i try open a new pseudo-pty, i get a similar message to
> > the one in the subject, and one like "fstat: Value too large for defined data
> > type" if i open an xterm.
>
> It appears that you're using some variant of the 2.6.7 kernel, yes?
yup, just pure mainline, no patches.
> That kernel (and many preceding ones) will create large pty indexes and old
> (and/or buggy) userspace fails to handle it correctly.
ok, i suspected the user space stuff would puke on that, thanks.
> Post-2.6.7, the allocation of pty indexes was switched to first-fit and
> things should now work OK.
oh good news - thank you very much :).
> Please test a current kernel and send a report.
>
> 2.6.7 plus
> ftp://ftp.kernel.org/pub/linux/kernel/v2.6/snapshots/patch-2.6.7-bk9.gz
> would be suitable.
ok. as soon as i can. move it up on my mental TODO list =).
BTW, thanks go to all the kernel hackers and patch submitters (and
anyone else that works on or for the kernel :), for doing
such a good job, it's appreciated.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 652 bytes --]
next prev parent reply other threads:[~2004-06-26 23:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 15:11 Cannot access '/dev/pts/292': Value too large for defined data type simon
2004-06-26 20:59 ` Andrew Morton
2004-06-26 23:21 ` simon [this message]
2004-06-27 10:24 ` simon
2004-06-27 17:52 ` Andrew Morton
2004-06-30 9:16 ` simon
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=20040626232104.GA32365@nuit.ca \
--to=simon@nuit.ca \
--cc=akpm@osdl.org \
--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