Re: 3.4+ tty lockdep trace

[Alan Cox]

On Thu, 24 May 2012 13:24:56 +0200
Sasha Levin <levinsasha928@xxxxxxxxx> wrote:

> On Thu, May 24, 2012 at 1:21 PM, Sasha Levin
> <levinsasha928@xxxxxxxxx> wrote:
> > On Thu, May 24, 2012 at 1:20 PM, Sasha Levin
> > <levinsasha928@xxxxxxxxx> wrote:
> >> On Thu, May 24, 2012 at 1:10 PM, Alan Cox
> >> <alan@xxxxxxxxxxxxxxxxxxx> wrote:
> >>>> I'm still seeing the warning with this patch:
> >>>
> >>> Can you attach the trace that went with the trigger as well ?
> >>
> >> Ofcourse, attached as a file.
> >
> > Heh, this was a different one as well. I'll try to get the one I got
> > in the morning again.
> 
> 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 ?

Alan
--
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/