From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Eric Paris <eparis@parisplace.org>,
"Kasatkin, Dmitry" <dmitry.kasatkin@intel.com>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LSM List <linux-security-module@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
James Morris <jmorris@namei.org>
Subject: Re: [PATCH 0/2] ima: policy search speedup
Date: Tue, 11 Dec 2012 12:05:08 -0800 [thread overview]
Message-ID: <CA+55aFwaFqJQXR3Z8M3byube6hODmiT-dDEH3uFPSKpTDGXHaQ@mail.gmail.com> (raw)
In-Reply-To: <1355255320.2356.148.camel@falcor>
On Tue, Dec 11, 2012 at 11:48 AM, Mimi Zohar <zohar@linux.vnet.ibm.com> wrote:
>
> Ok. To summarize, S_IMA indicates that there is a rule and that the iint
> was allocated. To differentiate between 'haven't looked/don't know' and
> 'definitely not', we need another bit. For this, you're suggesting
> using IS_PRIVATE()? Hopefully, I misunderstood.
No, for that, I'm suggesting using a new bit in i_flags.
The "IS_PRIVATE()" thing is more a "if you know a-priori that you
aren't interested in pseudo-filesystems, you can already check that
bit, because it will be set for things like /proc and shmem mappings
and pipes etc".
Dmitry seemed to imply that the biggest use for the new bit was for
taking out whole pseudo-filesystems in one go. That would pretty much
be what S_PRIVATE is.
Linus
next prev parent reply other threads:[~2012-12-11 20:05 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 21:54 [PATCH 0/2] ima: policy search speedup Dmitry Kasatkin
2012-11-22 21:54 ` [PATCH 1/2] vfs: new super block feature flags attribute Dmitry Kasatkin
2012-11-22 21:54 ` [PATCH 2/2] ima: skip policy search for never appraised or measured files Dmitry Kasatkin
2012-11-27 13:42 ` [PATCH 0/2] ima: policy search speedup Kasatkin, Dmitry
2012-12-11 12:51 ` Kasatkin, Dmitry
2012-12-11 14:08 ` Mimi Zohar
2012-12-11 16:59 ` Linus Torvalds
2012-12-11 17:40 ` Kasatkin, Dmitry
2012-12-11 17:55 ` Linus Torvalds
2012-12-11 18:09 ` Eric Paris
2012-12-11 18:35 ` Kasatkin, Dmitry
2012-12-11 19:07 ` Mimi Zohar
2012-12-11 22:16 ` Dave Chinner
2012-12-11 18:10 ` Kasatkin, Dmitry
2012-12-11 18:29 ` Al Viro
2012-12-11 18:12 ` Kasatkin, Dmitry
2012-12-11 18:35 ` Linus Torvalds
2012-12-11 18:53 ` Kasatkin, Dmitry
2012-12-11 18:18 ` Mimi Zohar
2012-12-11 18:35 ` Eric Paris
2012-12-11 18:59 ` Mimi Zohar
2012-12-11 19:10 ` Linus Torvalds
2012-12-11 19:48 ` Mimi Zohar
2012-12-11 20:05 ` Linus Torvalds [this message]
2012-12-11 20:15 ` Eric Paris
2012-12-11 20:31 ` Linus Torvalds
2012-12-11 20:08 ` Eric Paris
2012-12-11 22:57 ` Kasatkin, Dmitry
2012-12-11 23:02 ` Eric Paris
2012-12-12 13:56 ` Kasatkin, Dmitry
2012-12-12 14:25 ` Eric Paris
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=CA+55aFwaFqJQXR3Z8M3byube6hODmiT-dDEH3uFPSKpTDGXHaQ@mail.gmail.com \
--to=torvalds@linux-foundation.org \
--cc=dmitry.kasatkin@intel.com \
--cc=eparis@parisplace.org \
--cc=jmorris@namei.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=zohar@linux.vnet.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).