Re: BUG in find_pid_ns

2013-02-18 Thread Eric W. Biederman
Sasha Levin writes: > On 02/17/2013 07:17 PM, ebied...@xmission.com wrote: >> The bad pointer value is 0xfff0. Hmm. >> >> If you have the failure location correct it looks like a corrupted hash >> entry was found while following the hash chain. >> >> It looks like the memory has

Re: BUG in find_pid_ns

2013-02-18 Thread Eric W. Biederman
Sasha Levin sasha.le...@oracle.com writes: On 02/17/2013 07:17 PM, ebied...@xmission.com wrote: The bad pointer value is 0xfff0. Hmm. If you have the failure location correct it looks like a corrupted hash entry was found while following the hash chain. It looks like the

Re: BUG in find_pid_ns

2013-02-17 Thread Sasha Levin
On 02/17/2013 07:17 PM, ebied...@xmission.com wrote: > The bad pointer value is 0xfff0. Hmm. > > If you have the failure location correct it looks like a corrupted hash > entry was found while following the hash chain. > > It looks like the memory has been set to -16 -EBUSY? Weird.

Re: BUG in find_pid_ns

2013-02-17 Thread Eric W. Biederman
Adding Oleg since he knows about as much about signals and pids as anyone. Sasha Levin writes: > Hi all, > > While fuzzing with trinity inside a KVM tools guest, running latest -next > kernel, > I've stumbled on the following spew: To my knowledge there are no in progress patches to this

BUG in find_pid_ns

2013-02-17 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest, running latest -next kernel, I've stumbled on the following spew: [ 400.345287] BUG: unable to handle kernel paging request at fff0 [ 400.346614] IP: [] find_pid_ns+0x110/0x1f0 [ 400.347649] PGD 5429067 PUD 542b067 PMD

BUG in find_pid_ns

2013-02-17 Thread Sasha Levin
Hi all, While fuzzing with trinity inside a KVM tools guest, running latest -next kernel, I've stumbled on the following spew: [ 400.345287] BUG: unable to handle kernel paging request at fff0 [ 400.346614] IP: [81131d50] find_pid_ns+0x110/0x1f0 [ 400.347649] PGD 5429067

Re: BUG in find_pid_ns

2013-02-17 Thread Eric W. Biederman
Adding Oleg since he knows about as much about signals and pids as anyone. Sasha Levin sasha.le...@oracle.com writes: Hi all, While fuzzing with trinity inside a KVM tools guest, running latest -next kernel, I've stumbled on the following spew: To my knowledge there are no in progress

Re: BUG in find_pid_ns

2013-02-17 Thread Sasha Levin
On 02/17/2013 07:17 PM, ebied...@xmission.com wrote: The bad pointer value is 0xfff0. Hmm. If you have the failure location correct it looks like a corrupted hash entry was found while following the hash chain. It looks like the memory has been set to -16 -EBUSY? Weird. It