linux-kernel - Re: static key arrays?

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: <1441973699.2083.6.camel@sipsolutions.net>
Date:	Fri, 11 Sep 2015 14:14:59 +0200
From:	Johannes Berg <johannes@...solutions.net>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Jason Baron <jbaron@...mai.com>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: static key arrays?

On Fri, 2015-09-11 at 13:10 +0200, Peter Zijlstra wrote:
> 
> struct static_key_false array[n] = { STATIC_KEY_FALSE_INIT, };
> 
> or something like that.

Yeah, ok, this would be sufficient for me - no need to mix different
types. I don't think that initializer works, but I guess we can just
duplicate it in the code - unless we can rely on zero-initialization
being sufficient.

My mistake was assuming that the only API was the macros, but of if we
just use the new struct names (struct static_key_false) without the
macros then there isn't really an issue.

Thanks,
johannes
--
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/