From: Sam Vilain <sam@vilain.net>
To: tvrtko.ursulin@sophos.com
Cc: Arjan van de Ven <arjan@infradead.org>,
Herbert Poetzl <herbert@13thfloor.at>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] vfs: cleanup of permission()
Date: Thu, 02 Mar 2006 10:20:53 +1300 [thread overview]
Message-ID: <44061035.20604@vilain.net> (raw)
In-Reply-To: <OF8335F2B0.0A730216-ON80257124.0045E22D-80257124.00475BA4@sophos.com>
tvrtko.ursulin@sophos.com wrote:
>>As external module, you have little say so far simply because your usage
>>isn't visible. I'd urge you to quickly submit your code so that the
>>things you need from this are better visible to the people who are
>>thinking and working on the redesign.
> I know all that, but it is a complicated matter to discuss. That's why I
> was planning to make a comprehensive announcement which would discuss most
> of the hot topics. Ideally yes, I would like to merge, but it won't happen
> now. The first thing I would like to do is establish common ground with
> other security vendors so that we could approach the problem together.
> Personaly, I am not sure whether insisting that everything should be a
> part of kernel is a right thing to do even though I think I understand all
> the up- and down-sides of both policies.
>
> Having said all this above, I am afraid that there will be no other choice
> but to start working on the announcement asap. :)
Perhaps you can put up the work in progress on a git repository somewhere?
Sam.
next prev parent reply other threads:[~2006-03-01 21:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-28 5:26 [RFC] vfs: cleanup of permission() Herbert Poetzl
2006-02-28 5:29 ` [RFC 1/2] vfs: remove nameidata from *_permission() Herbert Poetzl
2006-02-28 5:30 ` [RFC 2/2] vfs: fixup nfs and fuse by passing nd_flags via mask Herbert Poetzl
2006-03-01 8:45 ` [RFC] vfs: cleanup of permission() Trond Myklebust
2006-03-01 12:28 ` tvrtko.ursulin
2006-03-01 12:37 ` Arjan van de Ven
2006-03-01 12:59 ` tvrtko.ursulin
2006-03-01 21:20 ` Sam Vilain [this message]
2006-03-01 13:06 ` Herbert Poetzl
2006-03-01 21:18 ` Sam Vilain
2006-03-01 13:11 ` Herbert Poetzl
2006-03-01 23:42 ` Trond Myklebust
2006-03-02 1:35 ` Sam Vilain
2006-03-02 2:26 ` Trond Myklebust
2006-03-01 22:11 ` Sam Vilain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44061035.20604@vilain.net \
--to=sam@vilain.net \
--cc=arjan@infradead.org \
--cc=herbert@13thfloor.at \
--cc=linux-kernel@vger.kernel.org \
--cc=tvrtko.ursulin@sophos.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.