From: Eric Paris <eparis@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux@tycho.nsa.gov, sds@tycho.nsa.gov
Subject: Re: [PATCH -v3] SELinux: special dontaudit for access checks
Date: Thu, 06 May 2010 17:23:50 -0400 [thread overview]
Message-ID: <1273181030.15368.180.camel@localhost> (raw)
In-Reply-To: <alpine.LRH.2.00.1005061000280.22641@tundra.namei.org>
On Thu, 2010-05-06 at 10:03 +1000, James Morris wrote:
> On Wed, 5 May 2010, Eric Paris wrote:
>
> > On Wed, 2010-05-05 at 08:50 +1000, James Morris wrote:
> > > On Mon, 3 May 2010, Eric Paris wrote:
> > >
> > > > Signed-off-by: Eric Paris <eparis@redhat.com>
> > > > ---
> > >
> > > This does not apply to my tree, please fix.
> >
> > Patches sent should be applied in this order:
> >
> > re-introduce MAY_ACCESS
> > http://marc.info/?l=linux-fsdevel&m=127085147411199&w=2
>
> This changes filesystem code (e.g. logic in NFS), but has no comments or
> signoff from fs/vfs folk, as I indicated to you off-list. Do you think
> it's ok to go in anyway?
It changes NO logic, just breaks one flag into 2. If it does change any
logic the patch is busted! So yes I believe it is perfectly safe to go
in. I, however, poked Al again (about the 3rd time) just in case he has
a better suggestion.
-Eric
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
next prev parent reply other threads:[~2010-05-06 21:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-03 22:29 [PATCH -v3] SELinux: special dontaudit for access checks Eric Paris
2010-05-03 22:46 ` Eric Paris
2010-05-04 13:49 ` Stephen Smalley
2010-05-04 22:50 ` James Morris
2010-05-05 14:08 ` Eric Paris
2010-05-06 0:03 ` James Morris
2010-05-06 21:23 ` Eric Paris [this message]
2010-07-22 23:21 ` James Morris
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=1273181030.15368.180.camel@localhost \
--to=eparis@redhat.com \
--cc=jmorris@namei.org \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.