On Sat, Oct 16, 2010 at 08:49:45PM -0400, Christoph Hellwig wrote:
On Sat, Oct 16, 2010 at 02:10:29PM -0700, H. Peter Anvin wrote:
> I'm confused ... what makes you think we are? This might have been an
I didn't mean to imply you enabled it intentionally. In fact it looks
like the inode tracking in IMA is always on once it's compiled in, which
totally defeats the purpose of doing it's on iternal inode tracking
instead of bloating the inode what they originally proposed. IMA really
needs a kernel parameter to only enabled this crap when people actually
And whoever turned it on in Fedora needs some serious wahcking.
Hey Eric, sorry to throw you under the bus, but...
1.316 (eparis 11-Aug-09): CONFIG_IMA=y
Perhaps we should stop merging crap into the kernel if it's not supposed
to be enabled. (Granted, IMA is better than 99% of the random junk
merged in a release, it actually has somewhat useful Kconfig help text,
unlike the thousands of crap drivers that get merged which provide no
hint to what obscure medieval ARM board found only on three silicon
revisions two of which were never released they were for.)
The Kconfig description sounds generally useful to me. If it's bloated
crap, how did it get merged?