From: Andrew Morton <akpm@osdl.org>
To: Greg KH <greg@kroah.com>
Cc: mingo@elte.hu, diffie@gmail.com, linux-kernel@vger.kernel.org,
diffie@blazebox.homeip.net, Alan Cox <alan@lxorguk.ukuu.org.uk>,
Andries Brouwer <Andries.Brouwer@cwi.nl>
Subject: Re: 2.6.10-rc1-mm3
Date: Mon, 8 Nov 2004 21:27:47 -0800 [thread overview]
Message-ID: <20041108212747.33b6e14a.akpm@osdl.org> (raw)
In-Reply-To: <20041108224259.GA14506@kroah.com>
Greg KH <greg@kroah.com> wrote:
>
> So I don't see how that could be failing here. And why I don't see this
> on my boxes...
OK, progress. The oops is due to CONFIG_LEGACY_PTY_COUNT=512. I assume
anything greater than 256 will trigger it.
- tty_register_driver() calls tty_register_device() for 512 devices.
- tty_register_device() calls pty_line_name() for the 512 devices, but
pty_line_name() only understands 256 devices. After that, it starts
returning duplicated names.
- class_simple_device_add() gets an -EEXIST return from
class_device_register() and then tries to kfree local variable s_dev, but
it's already free. Presumably all that icky refcounting under
class_device_register() did this for us already. Can you fix this one
Greg? Just enable slab debugging, set CONFIG_LEGACY_PTY_COUNT=512 and
watch the fun.
As for the limitation of 256 legacy ptys: we should either raise it by
cooking up new device names or limit it to 256 in config. The latter, I
guess. Is there a requirement to support more than 256 legacy ptys?
Limit the number of legacy ptys to 256. pty_line_name() isn't capable of
generating more than 256 unique names.
Signed-off-by: Andrew Morton <akpm@osdl.org>
---
25-akpm/drivers/char/Kconfig | 1 +
1 files changed, 1 insertion(+)
diff -puN drivers/char/Kconfig~limit-CONFIG_LEGACY_PTY_COUNT drivers/char/Kconfig
--- 25/drivers/char/Kconfig~limit-CONFIG_LEGACY_PTY_COUNT 2004-11-08 21:22:46.843719848 -0800
+++ 25-akpm/drivers/char/Kconfig 2004-11-08 21:23:23.496147832 -0800
@@ -478,6 +478,7 @@ config LEGACY_PTYS
config LEGACY_PTY_COUNT
int "Maximum number of legacy PTY in use"
depends on LEGACY_PTYS
+ range 1 256
default "256"
---help---
The maximum number of legacy PTYs that can be used at any one time.
_
next prev parent reply other threads:[~2004-11-09 5:54 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-06 19:04 2.6.10-rc1-mm3 Paul Blazejowski
2004-11-07 10:48 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-07 17:24 ` 2.6.10-rc1-mm3 Paul Blazejowski
2004-11-08 7:59 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-08 7:42 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-08 22:42 ` 2.6.10-rc1-mm3 Greg KH
2004-11-09 5:27 ` Andrew Morton [this message]
2004-11-09 7:14 ` 2.6.10-rc1-mm3 Greg KH
2004-11-09 8:05 ` 2.6.10-rc1-mm3 Greg KH
2004-11-09 8:15 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-09 8:27 ` 2.6.10-rc1-mm3 Greg KH
2004-11-09 12:11 ` 2.6.10-rc1-mm3 Tejun Heo
2004-11-09 7:53 ` 2.6.10-rc1-mm3 Olivier Poitrey
2004-11-09 8:22 ` 2.6.10-rc1-mm3 Arjan van de Ven
2004-11-09 9:25 ` 2.6.10-rc1-mm3 Olivier Poitrey
2004-11-09 10:37 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-09 9:39 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-09 10:44 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-09 10:33 ` 2.6.10-rc1-mm3 Andries Brouwer
2004-11-11 1:52 ` 2.6.10-rc1-mm3 H. Peter Anvin
2004-11-09 18:24 ` 2.6.10-rc1-mm3 Paul Blazejowski
-- strict thread matches above, loose matches on Subject: below --
2004-11-08 12:34 2.6.10-rc1-mm3 Karsten Wiese
2004-11-08 21:40 ` 2.6.10-rc1-mm3 Karsten Wiese
2004-11-08 22:25 ` 2.6.10-rc1-mm3 linux-os
2004-11-08 23:30 ` 2.6.10-rc1-mm3 Chris Wright
[not found] <20041105001328.3ba97e08.akpm@osdl.org.suse.lists.linux.kernel>
[not found] ` <418B5C70.7090206@kolivas.org.suse.lists.linux.kernel>
2004-11-05 11:53 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:16 ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 12:23 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 8:13 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 9:41 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Andrew Morton
2004-11-05 10:48 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:36 ` 2.6.10-rc1-mm3 Lorenzo Allegrucci
2004-11-05 10:22 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 10:38 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:09 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:17 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 11:24 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 11:43 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:15 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 12:22 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 12:57 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 13:02 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 17:47 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 11:20 ` 2.6.10-rc1-mm3 Russell King
2004-11-05 11:30 ` 2.6.10-rc1-mm3 Andi Kleen
2004-11-05 10:17 ` 2.6.10-rc1-mm3 Ingo Molnar
2004-11-05 15:54 ` 2.6.10-rc1-mm3 Michael Baehr
2004-11-05 10:56 ` 2.6.10-rc1-mm3 Con Kolivas
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Rafael J. Wysocki
2004-11-05 18:07 ` 2.6.10-rc1-mm3 Adam Heath
2004-11-06 7:16 ` 2.6.10-rc1-mm3 Pasi Savolainen
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=20041108212747.33b6e14a.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=diffie@blazebox.homeip.net \
--cc=diffie@gmail.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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
all inboxes | Powered by JetHome®