From: ebiederm@xmission.com (Eric W. Biederman)
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Greg Kroah-Hartman <gregkh@suse.de>
Subject: Re: v2.6.31-rc6: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Date: Thu, 20 Aug 2009 00:33:17 -0700 [thread overview]
Message-ID: <m1ocqbgcsi.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <7b6bb4a50908200010h1c60d007p4fa017fd97c87c19@mail.gmail.com> (Xiaotian Feng's message of "Thu\, 20 Aug 2009 15\:10\:53 +0800")
Xiaotian Feng <xtfeng@gmail.com> writes:
> On Thu, Aug 20, 2009 at 2:07 PM, Eric W. Biederman <ebiederm@xmission.com>
> wrote:
>
>
> ebiederm@xmission.com (Eric W. Biederman) writes:
>
> > I'm not certain who I should route this too, but I just had 2.6.31-rc6
> > fall over on me. I don't know how reproducible this will be but
> > I have a full crash dump if someone is interested in looking into this.
>
> Looks like I was wrong. This is appears trivial to reproduce,
> I have just reproduced it two more times in a row. I think
> the problem is pty related.
>
> I was looking into a change in behavior on 2.6.31-rc6 where
> data was being lost, and it appears one variant of my test program
> kills the kernel.
>
> The following program run as an unprivileged user causes a kernel
> panic in about a minute:
>
> aka
>
> while :; do ./KernelTtyTest ; done
>
>
> oops.... It panics my x86_64 machine.....
I guess I forgot to mention that detail. Thanks for confirming this
bug isn't just me.
Eric
next prev parent reply other threads:[~2009-08-20 7:33 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 5:46 v2.6.31-rc6: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008 Eric W. Biederman
2009-08-20 6:07 ` Eric W. Biederman
[not found] ` <7b6bb4a50908200010h1c60d007p4fa017fd97c87c19@mail.gmail.com>
2009-08-20 7:33 ` Eric W. Biederman [this message]
2009-08-20 9:23 ` Xiaotian Feng
2009-08-21 2:09 ` Zhang, Yanmin
2009-08-21 18:23 ` Eric W. Biederman
2009-08-20 7:54 ` Dave Young
2009-08-20 8:00 ` Eric W. Biederman
2009-08-20 8:19 ` Dave Young
2009-08-24 22:34 ` Linus Torvalds
2009-08-24 23:51 ` Linus Torvalds
2009-08-25 0:09 ` Linus Torvalds
2009-08-25 1:41 ` Eric W. Biederman
2009-08-25 2:48 ` Dave Young
2009-08-25 3:08 ` Xiaotian Feng
2009-08-25 6:16 ` Zhang, Yanmin
2009-08-25 3:39 ` Frederic Weisbecker
2009-08-25 4:10 ` Linus Torvalds
2009-08-25 4:30 ` Linus Torvalds
2009-08-25 15:05 ` Frederic Weisbecker
2009-08-25 14:24 ` Frederic Weisbecker
2009-08-27 9:15 ` Zhang, Yanmin
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=m1ocqbgcsi.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=gregkh@suse.de \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=x86@kernel.org \
--cc=xtfeng@gmail.com \
/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