From: Chris Wright <chrisw@sous-sol.org>
To: "Serge E. Hallyn" <serue@us.ibm.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, safford@watson.ibm.com,
serue@linux.vnet.ibm.com, kjhall@linux.vnet.ibm.com,
zohar@us.ibm.com
Subject: Re: [RFC][Patch 2/6] integrity: fs hook placement
Date: Thu, 8 Mar 2007 09:40:36 -0800 [thread overview]
Message-ID: <20070308174036.GF10574@sequoia.sous-sol.org> (raw)
In-Reply-To: <20070308170733.GA21099@sergelap.austin.ibm.com>
* Serge E. Hallyn (serue@us.ibm.com) wrote:
> Are you objecting only to the duplication at the callsites, so that an
> fsnotify-type of consolidation of security and integrity hooks would be
> ok? Or are you complaining that the security_inode_setxattr and
> integrity_inode_setxattr hooks are too similar anyway, and integrity
> modules should just use some lsm hooks for anything which will be
> authoritative?
It's duplication of callsites with many identical implementations
that's the problem.
> (I could see an argument that integirty subsystem should be purely for
> measuring and hence its hooks should never return a value. Only hitch
> there is that if integrity subsystem hits ENOMEM it should be able to
> refuse the action...)
Right, that's what I was expecting to see, just the measurement
infrastructure.
thanks,
-chris
next prev parent reply other threads:[~2007-03-08 17:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-08 16:03 [RFC][Patch 2/6] integrity: fs hook placement Mimi Zohar
2007-03-08 16:41 ` Chris Wright
2007-03-08 17:07 ` Serge E. Hallyn
2007-03-08 17:40 ` Chris Wright [this message]
2007-03-08 18:01 ` Serge E. Hallyn
2007-03-08 19:22 ` Stephen Smalley
2007-03-08 21:07 ` Serge E. Hallyn
2007-03-08 18:34 ` Mimi Zohar
2007-03-08 18:16 ` Dmitriy Monakhov
2007-03-08 18:45 ` Mimi Zohar
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=20070308174036.GF10574@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=kjhall@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=serue@linux.vnet.ibm.com \
--cc=serue@us.ibm.com \
--cc=zohar@linux.vnet.ibm.com \
--cc=zohar@us.ibm.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.