linux-kernel - Re: [PATCH 01/11] IMA: use rbtree instead of radix tree for inode information cache

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:	Mon, 25 Oct 2010 14:11:45 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"J.H." <warthog9@...nel.org>, John Stoffel <john@...ffel.org>,
	Eric Paris <eparis@...hat.com>, linux-kernel@...r.kernel.org,
	linux-security-module@...r.kernel.org,
	linux-fsdevel@...r.kernel.org, zohar@...ibm.com,
	david@...morbit.com, jmorris@...ei.org, kyle@...artin.ca,
	hpa@...or.com, akpm@...ux-foundation.org, mingo@...e.hu,
	viro@...iv.linux.org.uk
Subject: Re: [PATCH 01/11] IMA: use rbtree instead of radix tree for inode
 information cache

On Mon, Oct 25, 2010 at 1:57 PM, Christoph Hellwig <hch@...radead.org> wrote:
>
> Kyle sent a very useful patch to simply disable the ima tracking unless
> you enable it on the command line.

And exactly how does that invalidate _any_ of the patches in the IMA
series in question? All of them are basically still equally valid.

And the "four bytes in 'struct inode' is a total no-no" crowd clearly
haven't looked at struct inode. As mentioned, we've got things like
quota stuff there too.

And quite frankly, it sounds like the right thing to do for Fedora &co
is to simply _disable_ CONFIG_IMA. If there is no support for it on a
distro level, then you shouldn't enable it.

                           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/