[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20121025110954.GA24886@redhat.com>
Date: Thu, 25 Oct 2012 07:09:54 -0400
From: Dave Jones <davej@...hat.com>
To: Darren Hart <dvhart@...ux.intel.com>
Cc: Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: pi futex oops in __lock_acquire
On Wed, Oct 24, 2012 at 09:44:07PM -0700, Darren Hart wrote:
>
>
> On 10/24/2012 01:24 PM, Dave Jones wrote:
> > I've been able to trigger this for the last week or so.
> > Unclear whether this is a new bug, or my fuzzer got smarter, but I see the
> > pi-futex code hasn't changed since the last time it found something..
> >
> > > BUG: unable to handle kernel NULL pointer dereference at 0000000000000018
> >
> > It looks like we got all the way to lock_acquire with a NULL 'lock' somehow.
> >
> > Darren, any idea how this could happen ?
>
> I'm digging. Can you get trinity to provide the arguments it used that
> trigger the crash? That might help hone in on the exact path.
Happens pretty quickly with -c futex for me. (30 seconds or so)
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists