[lkml]   [2009]   [Aug]   [20]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: v2.6.31-rc6: BUG: unable to handle kernel NULL pointer dereference at 0000000000000008
Dave Young <> writes:

> On Thu, Aug 20, 2009 at 2:07 PM, Eric W. Biederman<> wrote:
>> (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
> The test app failed for me:
> read failed: Input/output error
> lastbytes: '\r\nprocess_cmd read failed: Interrupted system
> call\r\necho _2_\r\n'
> Aborted

Oh. It definitely fails. I just found that when it failed
about 600 times in a row it took my kernel with it. I was
developing it to understand tty interactions, and when I realized
that the version I had was killing my kernel I sent it out
as it was a nice self contained test case.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-08-20 10:03    [W:0.112 / U:15.400 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site