[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20101019162907.GA5785@infradead.org>
Date: Tue, 19 Oct 2010 12:29:07 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Eric Paris <eparis@...hat.com>
Cc: Dave Chinner <david@...morbit.com>,
Christoph Hellwig <hch@...radead.org>,
linux-kernel@...r.kernel.org,
linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, zohar@...ibm.com,
warthog9@...nel.org, jmorris@...ei.org, kyle@...artin.ca,
hpa@...or.com, akpm@...ux-foundation.org,
torvalds@...ux-foundation.org, mingo@...e.hu,
viro@...iv.linux.org.uk
Subject: Re: [PATCH 1/3] IMA: move read/write counters into struct inode
Eric,
I think you and just about everyone here are on a different page, and
before we have the basic disagreement settled I'm not sure we can
make much progress.
Can you please explain why a feature like IMA that no sane user would
ever want should cause _any_ overhead for users that just have it
compiled in because their distro or defconfig did without actually
using.
What exactly is the problem to require the few people that want it to
use a kernel command line option and/or an _DEFAULT_ON config option?
--
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/
Powered by blists - more mailing lists