[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.LRH.2.00.1010181127480.9476@tundra.namei.org>
Date: Mon, 18 Oct 2010 11:49:02 +1100 (EST)
From: James Morris <jmorris@...ei.org>
To: Christoph Hellwig <hch@...radead.org>
cc: Ingo Molnar <mingo@...e.hu>, Kyle McMartin <kyle@...artin.ca>,
kernel@...ts.fedoraproject.org, Mimi Zohar <zohar@...ibm.com>,
warthog9@...nel.org, Dave Chinner <david@...morbit.com>,
linux-kernel@...r.kernel.org, "H. Peter Anvin" <hpa@...or.com>,
Serge Hallyn <serue@...ibm.com>,
Andrew Morton <akpm@...ux-foundation.org>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: ima: use of radix tree cache indexing == massive waste of
memory?
On Sun, 17 Oct 2010, Christoph Hellwig wrote:
> Especially as our merge requirements for security/ are a lot lower than
> for the rest of the kernel given that James is very afraid of getting
> whacked by Linux for not mering things.
I think historically you'll see that I'm not afraid of getting whacked by
Linus.
A procedure for merging security features has been adopted by consensus,
based on suggestions from Arjan, with the aim of preventing the literally
endless arguments which arise from security feature discussions. It's
sometimes referred to as the Arjan protocol, essentially:
If the feature correctly implements a well-defined security goal, meets
user needs without incurring unreasonable overheads, passes technical
review, and is supported by competent developers, then it is likely to
be merged.
If you disagree with a specific feature, you need to step up while it's
being reviewed and make a case against it according to the above criteria.
If you disagree with the protocol, then you need to come up with a better
one, and probably implement it yourself, to the satisfaction of all
parties.
- 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/
Powered by blists - more mailing lists