From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: nuclearcat <nuclearcat@nuclearcat.com>,
torvalds@osdl.org, Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: pty_chars_in_buffer NULL pointer (kernel oops)
Date: Fri, 25 Feb 2005 20:04:32 -0300 [thread overview]
Message-ID: <20050225230432.GD15251@logos.cnet> (raw)
In-Reply-To: <1567604259.20050218105653@nuclearcat.com>
Hi,
On Fri, Feb 18, 2005 at 10:56:53AM +0200, nuclearcat wrote:
> Is discussed at
> http://kerneltrap.org/mailarchive/1/message/12508/thread
> bug fixed in 2.4.x tree? Cause seems i have downloaded 2.4.29, and it
> is not fixed (still my kernel on vpn server crashing almost at start),
> i have grepped fast pre and bk patches, but didnt found any fixed
> related to tty/pty.
Can you please post the oops? Have you done so already?
What makes you think it is the same race discussed in the above thread?
BTW, I fail to see any drivers/char/pty.c change related to the race which triggers
the pty_chars_in_buffer->0 oops.
Quoting the first message from thread you mention:
"That last call trace entry is the call in pty_chars_in_buffer() to
/* The ldisc must report 0 if no characters available to be read */
count = to->ldisc.chars_in_buffer(to);
"
Alan, Linus, what correction to the which the above thread discusses has
been deployed?
> Provided in thread patch from Linus working, but after night i have
> checked server, and see load average jumped to 700.
> Can anybody help in that? I am not kernel guru to provide a patch, but
> seems by search in google it is actual problem for people, who own
> poptop vpn servers, it is really causing serious instability for
> servers.
Can you compile a list of such v2.4 reports?
next prev parent reply other threads:[~2005-02-26 3:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 8:56 pty_chars_in_buffer NULL pointer (kernel oops) nuclearcat
2005-02-25 23:04 ` Marcelo Tosatti [this message]
2005-02-26 3:42 ` Linus Torvalds
2005-02-26 11:18 ` Alan Cox
2005-02-27 14:52 ` Re[2]: " nuclearcat
2005-02-27 15:03 ` Re[3]: " nuclearcat
-- strict thread matches above, loose matches on Subject: below --
2005-02-27 10:00 Marcelo Tosatti
2005-02-27 19:46 ` Linus Torvalds
2005-04-13 18:43 ` Jason Baron
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=20050225230432.GD15251@logos.cnet \
--to=marcelo.tosatti@cyclades.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nuclearcat@nuclearcat.com \
--cc=torvalds@osdl.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