linux-kernel - Re: Make RCU dcache work with CONFIG

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]

Date:	Fri, 22 Apr 2011 16:29:43 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Eric Paris <eparis@...hat.com>
Cc:	Andi Kleen <andi@...stfloor.org>, linux-fsdevel@...r.kernel.org,
	akpm@...ux-foundation.org, linux-kernel@...r.kernel.org,
	npiggin@...nel.dk, shaohua.li@...el.com, sds@...ho.nsa.gov,
	jmorris@...ei.org, linux-security-module@...r.kernel.org,
	Eric Paris <eparis@...isplace.org>
Subject: Re: Make RCU dcache work with CONFIG_SECURITY=y

On Fri, Apr 22, 2011 at 2:17 PM, Eric Paris <eparis@...hat.com> wrote:
> On Fri, 2011-04-22 at 11:26 -0700, Linus Torvalds wrote:
>>
>> Comments? I'd really like to see/hear feedback like "yeah, this looks
>> really obviously safe" vs "yeah, looks good, but I really don't feel
>> very comfortable with it" from the security people.
>
> From an SELinux PoV (And I feel semi confident about SMACK) patch 1/3
> can and should go in as soon as you want.  2/3 looked safe on first
> glance, but I think I can make it smaller and better.  I'll try to get a
> version of 2/3 on list in the next couple of days.  My first thought was
> that it should probably go in via my SELinux tree next window......

Ok, given the pretty obvious nature of 1/3 and no objections, I
committed that one.

Let's see what the situation with 2/3 is. It would be good to not have
slower path lookup for all the selinux-using people, but whatever.

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