From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: Mimi Zohar <zohar@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
James Morris <jmorris@namei.org>,
Christoph Hellwig <hch@infradead.org>,
Dave Hansen <dave@linux.vnet.ibm.com>,
"<David Safford" <safford@watson.ibm.com>,
Serge Hallyn <serue@us.ibm.com>
Subject: [PATCH 0/6] integrity
Date: Thu, 29 Jan 2009 17:23:21 -0500 [thread overview]
Message-ID: <cover.1233262162.git.zohar@linux.vnet.ibm.com> (raw)
This patchset contains the IMA integrity patches. Based on
comments on the mailing list, both the LIM ops registration,
which provides support for multiple integrity modules, and
template ops registration, which provides template support,
have been removed. As part of this change, the integrity
hooks have been renamed to ima.
Other changes made since the last integrity posting, are based
on comments made by: Christoph Hellwig, Dave Hansen, Paul McKenney,
Serge Hallyn, Matt Helsley, and Sukadev Bhattiprolu. Listed here
are major changes. Additional changes are listed in the patch
descriptions.
- added slab for integrity information(iint) associated with an inode
- added a local read and write count in iint
- lots of code refactoring
- addressed locking, in general, and rcu-locking issues
- removed caching of measurement policy results
- cleanup of the policy parsing
New to the integrity patchset, based on Serge Hallyn and Dave
Hansen's suggestion, is a method to detect an imbalance between
the number of calls to ima_path_check() and ima_file_free(),
which could indicate that a file was accessed without first being
measured.
The integrity-tpm-internal-interface.patch will be posted separately
by Rajiv Andrade.
Mimi Zohar (6):
integrity: IMA hooks
integrity: IMA as an integrity service provider
integrity: IMA display
integrity: IMA policy
integrity: IMA policy open
Integrity: IMA file free imbalance
next reply other threads:[~2009-01-29 22:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-29 22:23 Mimi Zohar [this message]
2009-01-29 22:23 ` [PATCH 1/6] integrity: IMA hooks Mimi Zohar
2009-01-29 22:23 ` [PATCH 2/6] integrity: IMA as an integrity service provider Mimi Zohar
2009-01-30 0:07 ` James Morris
2009-01-30 19:29 ` Mimi Zohar
2009-01-30 9:04 ` James Morris
2009-01-30 13:13 ` Mimi Zohar
2009-02-02 23:02 ` Serge E. Hallyn
2009-02-03 2:09 ` Mimi Zohar
2009-02-03 13:36 ` david safford
2009-02-03 14:03 ` Serge E. Hallyn
2009-01-29 22:23 ` [PATCH 3/6] integrity: IMA display Mimi Zohar
2009-01-30 9:18 ` James Morris
2009-01-30 13:14 ` Mimi Zohar
2009-02-02 23:14 ` Serge E. Hallyn
2009-02-03 0:03 ` James Morris
2009-01-29 22:23 ` [PATCH 4/6] integrity: IMA policy Mimi Zohar
2009-02-02 23:40 ` Serge E. Hallyn
2009-02-03 1:29 ` Mimi Zohar
2009-01-29 22:23 ` [PATCH 5/6] integrity: IMA policy open Mimi Zohar
2009-01-29 22:23 ` [PATCH 6/6] Integrity: IMA file free imbalance Mimi Zohar
2009-02-02 23:47 ` Serge E. Hallyn
2009-02-03 1:27 ` Mimi Zohar
2009-02-06 0:00 ` [PATCH 0/6] integrity James Morris
2009-02-06 2:29 ` Mimi Zohar
2009-02-06 8:14 ` James Morris
-- strict thread matches above, loose matches on Subject: below --
2008-12-02 21:47 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=cover.1233262162.git.zohar@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dave@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=safford@watson.ibm.com \
--cc=serue@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