linux-kernel - Re: [PATCH -v8 -rc3] Security: Introduce security= boot parameter

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, 7 Mar 2008 00:31:58 +1100 (EST)
From:	James Morris <jmorris@...ei.org>
To:	"Ahmed S. Darwish" <darwish.07@...il.com>
cc:	Chris Wright <chrisw@...s-sol.org>,
	Stephen Smalley <sds@...ho.nsa.gov>,
	Eric Paris <eparis@...isplace.org>,
	Casey Schaufler <casey@...aufler-ca.com>,
	Paul Moore <paul.moore@...com>,
	Alexey Dobriyan <adobriyan@...ru>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Linus <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>,
	LSM-ML <linux-security-module@...r.kernel.org>
Subject: Re: [PATCH -v8 -rc3] Security: Introduce security= boot parameter

On Thu, 6 Mar 2008, Ahmed S. Darwish wrote:

>     Handle Andrew's concerns:
>     - Use __init and __initdata in appropriate places.
>     - Do not rely upon dummy_ops layout, use C99 initializations.
>     - Use DEFINE_SPINLOCK instead of dynamic initialization.

The spinlock is not needed now, if security_module_enable() can only be 
called during boot via an initcall.


- James
-- 
James Morris
<jmorris@...ei.org>
--
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/