linux-kernel - Re: 3.4+ tty lockdep trace

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120525023222.GC30024@home.goodmis.org>
Date:	Thu, 24 May 2012 22:32:22 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Alan Cox <alan@...ux.intel.com>
Cc:	Sasha Levin <levinsasha928@...il.com>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	Ming Lei <tom.leiming@...il.com>,
	Dave Jones <davej@...hat.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: Re: 3.4+ tty lockdep trace

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@...il.com> 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/