Re: yama: lockdep warning on yama_ptracer_del

2012-11-19 Thread Kees Cook
On Mon, Nov 19, 2012 at 10:59 AM, Sasha Levin wrote: > On 11/19/2012 11:23 AM, Kees Cook wrote: >> On Sun, Nov 18, 2012 at 8:05 PM, Sasha Levin wrote: >>> Hi Kees, >>> >>> On Thu, Oct 18, 2012 at 6:39 PM, Kees Cook wrote: On Wed, Oct 17, 2012 at 8:10 PM, Sasha Levin wrote: > Hi a

Re: yama: lockdep warning on yama_ptracer_del

2012-11-19 Thread Sasha Levin
On 11/19/2012 11:23 AM, Kees Cook wrote: > On Sun, Nov 18, 2012 at 8:05 PM, Sasha Levin wrote: >> Hi Kees, >> >> On Thu, Oct 18, 2012 at 6:39 PM, Kees Cook wrote: >>> On Wed, Oct 17, 2012 at 8:10 PM, Sasha Levin wrote: Hi all, I was fuzzing with trinity within a KVM tools guest (l

Re: yama: lockdep warning on yama_ptracer_del

2012-11-19 Thread Kees Cook
On Sun, Nov 18, 2012 at 8:05 PM, Sasha Levin wrote: > Hi Kees, > > On Thu, Oct 18, 2012 at 6:39 PM, Kees Cook wrote: >> On Wed, Oct 17, 2012 at 8:10 PM, Sasha Levin wrote: >>> Hi all, >>> >>> I was fuzzing with trinity within a KVM tools guest (lkvm) on a linux-next >>> kernel, and got the >>>

Re: yama: lockdep warning on yama_ptracer_del

2012-11-18 Thread Sasha Levin
Hi Kees, On Thu, Oct 18, 2012 at 6:39 PM, Kees Cook wrote: > On Wed, Oct 17, 2012 at 8:10 PM, Sasha Levin wrote: >> Hi all, >> >> I was fuzzing with trinity within a KVM tools guest (lkvm) on a linux-next >> kernel, and got the >> following dump which I believe to be noise due to how the timers

Re: yama: lockdep warning on yama_ptracer_del

2012-10-18 Thread Kees Cook
On Wed, Oct 17, 2012 at 8:10 PM, Sasha Levin wrote: > Hi all, > > I was fuzzing with trinity within a KVM tools guest (lkvm) on a linux-next > kernel, and got the > following dump which I believe to be noise due to how the timers work - but > I'm not 100% sure. > ... > [ 954.674123] Possible i

yama: lockdep warning on yama_ptracer_del

2012-10-17 Thread Sasha Levin
Hi all, I was fuzzing with trinity within a KVM tools guest (lkvm) on a linux-next kernel, and got the following dump which I believe to be noise due to how the timers work - but I'm not 100% sure. If that's actually noise, the solution would be to get the timer code to assign meaningful names