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 be
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.
>
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 area
3 matches
Mail list logo
