linux-kernel - Re: [patch] lockdep: fix seqlock

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] [day] [month] [year] [list]

Message-ID: <20061213011555.GB6361@elte.hu>
Date:	Wed, 13 Dec 2006 02:15:55 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Andrew Morton <akpm@...l.org>
Cc:	Linus Torvalds <torvalds@...l.org>, linux-kernel@...r.kernel.org
Subject: Re: [patch] lockdep: fix seqlock_init()


* Andrew Morton <akpm@...l.org> wrote:

> > > > +#define seqlock_init(x)					\
> > > > +	do {						\
> > > > +		(x)->sequence = 0;			\
> > > > +		spin_lock_init(&(x)->lock);		\
> > > > +	} while (0)
> > > 
> > > This does not have to be a macro, does it?
> > 
> > Maybe it could be an __always_inline inline function (it has to be 
> > inlined to get the callsite based lock class key right)
> 
> the compiler darn better inline it, else we'll have an out-of-line 
> copy of everything in everywhere.

the compiler will do the uninlining happily if it sees a size advantage 
(when a single .c module calls the function several times), and creates 
a private per-object-file uninlined function. So an __always_inline 
would definitely be needed.

> > - but i'm not 
> > sure about the include file dependencies. Will probably work out fine as 
> > seqlock.h is supposed to be a late one in the order of inclusion - but i 
> > didnt want to make a blind bet.
> 
> seqlock.h already includes spinlock.h.

yes ... i just preserved the status quo.

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