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]

Date:	Fri, 6 Oct 2006 09:29:27 -0400
From:	"Dmitry Torokhov" <dmitry.torokhov@...il.com>
To:	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	"Ingo Molnar" <mingo@...e.hu>
Cc:	"Jiri Kosina" <jikos@...os.cz>,
	"Alessandro Suardi" <alessandro.suardi@...il.com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.18-git21, possible recursive locking in kseriod ends up in DWARF2 unwinder stuck

On 10/6/06, Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:
> > - 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...
> >
>
> or something like this:
>
> #define concat_i(a)     #a
> #define concat(a,b)     concat_i(a ## b)
>
> #define lockdep_set_subclass(lock, subclass) \
>  ({ static struct lock_key_class __key; \
>     lockdep_init_map(&(lock)->dep_map, concat(lock, subclass), \
>                      &__key, subclass); })
>

That leaves unneeded __key (another one was already created by
mutex_init...) but it tucked away nicely in the define so it is fune
by me.

Ingo, do you want to send these changes on or you want me to push them
through my tree?

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