Re: 3.4+ tty lockdep trace
From: Steven Rostedt
Date: Thu May 24 2012 - 22:32:21 EST
On Thu, May 24, 2012 at 03:54:57PM +0100, Alan Cox wrote:
> On Thu, 24 May 2012 13:24:56 +0200
> Sasha Levin <levinsasha928@xxxxxxxxx> wrote:
> >
> > And here is the second one attached as well, so these are two
> > different warnings I get with the new version.
>
>
> I'm somewhat baffled by this one. Can lockdep be fooled by an object
> being freed and reallocated at the same address, Is there any markup
> that should be present to avoid that ?
Sasha,
Did you apply Ming's second patch. His first patch (the one referenced
in the email) didn't have the unlock fixup.
--Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/