From: Linus Torvalds <torvalds@linux-foundation.org>
To: Mimi Zohar <zohar@linux.vnet.ibm.com>
Cc: Hugh Dickins <hugh.dickins@tiscali.co.uk>,
Mimi Zohar <zohar@us.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Serge Hallyn <serue@us.ibm.com>, James Morris <jmorris@namei.org>,
Al Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] integrity: fix IMA inode leak
Date: Sun, 7 Jun 2009 16:09:27 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.2.01.0906071608040.6847@localhost.localdomain> (raw)
In-Reply-To: <1244354901.3963.23.camel@dyn9002018117.watson.ibm.com>
On Sun, 7 Jun 2009, Mimi Zohar wrote:
>
> Mandatory Access Control(MAC) modules (i.e. SELinux, smack, etc) and
> integrity (i.e IMA) are two different aspects of security. The LSM
> hooks, which includes security_inode_free(), are used to implement MAC,
> not integrity.
So?
It's under security/integrity. And it's a level of detail that fs/inode.c
really doesn't care about.
The VFS layer cares NOT AT ALL about your "different aspects of security",
nor should it. The fact that security people think SELinux and IMA are
different is irrelavant - fs/inode.c just doesn't care. Why should it?
Linus
next prev parent reply other threads:[~2009-06-07 23:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-06 20:18 Hugh Dickins
2009-06-06 21:18 ` Linus Torvalds
2009-06-06 21:35 ` Linus Torvalds
2009-06-06 22:29 ` Hugh Dickins
2009-06-07 6:08 ` Mimi Zohar
2009-06-07 23:09 ` Linus Torvalds [this message]
2009-06-08 12:28 ` Mimi Zohar
2009-06-08 16:15 ` Linus Torvalds
2009-06-08 18:44 ` Mimi Zohar
2009-06-08 23:16 ` James Morris
2009-06-09 2:56 ` Mimi Zohar
2009-06-09 3:42 ` Casey Schaufler
2009-06-07 6:07 ` 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=alpine.LFD.2.01.0906071608040.6847@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=akpm@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=viro@zeniv.linux.org.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®