linux-kernel - Re: 2.6.18-git21, possible recursive locking in kseriod ends up in DWARF2 unwinder stuck

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: <Pine.LNX.4.64.0610061119240.12556@twin.jikos.cz>
Date:	Fri, 6 Oct 2006 11:22:17 +0200 (CEST)
From:	Jiri Kosina <jikos@...os.cz>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
cc:	Alessandro Suardi <alessandro.suardi@...il.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: 2.6.18-git21, possible recursive locking in kseriod ends up in
 DWARF2 unwinder stuck

On Thu, 5 Oct 2006, Dmitry Torokhov wrote:

> I tested the patches and they work. Couple of comments:
> - register_lock_class is marked as inline but now has 2 call sites and
> is relatively big - might want to remove "inline"

I agree.

> - how about adding lockdep_set_subclass() to avoid littering source
> with struct lock_class_key when we only want to tweak subclass? For
> that we might want export register_lock_class and hide it behind a
> #define...

I added Ingo to CC so that he could comment.

However I would not be able to submit patches which will be tested, as the 
only machine I had with passthrough synpatics port broke horribly and is 
currently in the warranty repair.

-- 
Jiri Kosina
-
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/