On Thu, 24 Apr 2014, Sasha Levin wrote:
> On 04/24/2014 03:24 PM, Greg KH wrote:
> > On Thu, Apr 24, 2014 at 01:40:14PM -0400, Sasha Levin wrote:
> >> > Hi all,
> >> >
> >> > While fuzzing with trinity inside a KVM tools guest running the latest
> >> > -next
> >> > kernel I've stumbled on the fo
On 04/24/2014 03:24 PM, Greg KH wrote:
> On Thu, Apr 24, 2014 at 01:40:14PM -0400, Sasha Levin wrote:
>> > Hi all,
>> >
>> > While fuzzing with trinity inside a KVM tools guest running the latest
>> > -next
>> > kernel I've stumbled on the following:
>> >
>> > [ 1361.390880] WARNING: CPU: 10 PID
On Thu, Apr 24, 2014 at 01:40:14PM -0400, Sasha Levin wrote:
> Hi all,
>
> While fuzzing with trinity inside a KVM tools guest running the latest -next
> kernel I've stumbled on the following:
>
> [ 1361.390880] WARNING: CPU: 10 PID: 24274 at lib/debugobjects.c:260
> debug_print_object+0x8c/0xb0
Hi all,
While fuzzing with trinity inside a KVM tools guest running the latest -next
kernel I've stumbled on the following:
[ 1361.390880] WARNING: CPU: 10 PID: 24274 at lib/debugobjects.c:260
debug_print_object+0x8c/0xb0()
[ 1361.391203] ODEBUG: free active (active state 0) object type: timer_l
4 matches
Mail list logo