linux-kernel - Re: [PATCH 1/2] lockdep: lockdep_set_class_and

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]

Date:	Tue, 26 Sep 2006 08:20:57 -0400
From:	Dmitry Torokhov <dtor@...ightbb.com>
To:	Ingo Molnar <mingo@...e.hu>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	linux-kernel@...r.kernel.org, Jiri Kosina <jikos@...os.cz>,
	Andrew Morton <akpm@...l.org>,
	Arjan van de Ven <arjan@...radead.org>,
	Dave Jones <davej@...hat.com>
Subject: Re: [PATCH 1/2] lockdep: lockdep_set_class_and_subclass

On Tuesday 26 September 2006 07:54, Ingo Molnar wrote:
> 
> * Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> 
> > Add lockdep_set_class_and_subclass() to the lockdep annotations.
> > 
> > This annotation makes it possible to assign a subclass on lock init. 
> > This annotation is meant to reduce the _nested() annotations by 
> > assigning a default subclass.
> > 
> > One could do without this annotation and rely on lockdep_set_class() 
> > exclusively, but that would require a manual stack of struct 
> > lock_class_key objects.
> > 
> > Signed-off-by: Peter Zijlstra <a.p.zijlstra@...llo.nl>
> 
> thanks, this extension to lockdep.c looks good to me - provided it 
> solves the problem :-)
> 
> Acked-by: Ingo Molnar <mingo@...e.hu>
> 

I will try testing it tonight - I have a Synaptics with a pass-through
port. Anyway, it really looks good now as far as serio code concerned.

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