From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] security/ima: use fs method to read integrity data
Date: Sun, 04 Jun 2017 21:57:21 -0400 [thread overview]
Message-ID: <1496627841.2998.44.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1706051022330.5970@namei.org>
On Mon, 2017-06-05 at 10:23 +1000, James Morris wrote:
> On Sun, 4 Jun 2017, Christoph Hellwig wrote:
>
> > On Thu, May 11, 2017 at 09:59:51AM +1000, James Morris wrote:
> > > On Wed, 10 May 2017, Christoph Hellwig wrote:
> > >
> > > > Add a new ->integrity_read file operation to read data for
> > > > integrity hash collection. This is defined to be equivalent
> > > > to ->read_iter, except that it will be called with the i_rwsem
> > > > held exclusively. Also the presence of ->integrity_read indicates
> > > > that the file system can support IMA.
> > > >
> > > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > >
> > > Fixes an IMA+XFS deadlock I've been seeing.
> >
> > Are you going to pick this up? Any feedback from the folks on the
> > LSM list on what additional file systems need to be wired up?
>
> That would normally come in via Mimi's tree, but I will pick it up if it
> doesn't.
With just this patch, a number of file measurements and appraisal
verifications are missing. ?I'm hoping to have an initial patch set
ready to be posted later this week.
Sorry for the delay.
Mimi
--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: James Morris <jmorris@namei.org>, Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
linux-ima-devel@lists.sourceforge.net,
linux-security-module@vger.kernel.org
Subject: Re: [PATCH] security/ima: use fs method to read integrity data
Date: Sun, 04 Jun 2017 21:57:21 -0400 [thread overview]
Message-ID: <1496627841.2998.44.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1706051022330.5970@namei.org>
On Mon, 2017-06-05 at 10:23 +1000, James Morris wrote:
> On Sun, 4 Jun 2017, Christoph Hellwig wrote:
>
> > On Thu, May 11, 2017 at 09:59:51AM +1000, James Morris wrote:
> > > On Wed, 10 May 2017, Christoph Hellwig wrote:
> > >
> > > > Add a new ->integrity_read file operation to read data for
> > > > integrity hash collection. This is defined to be equivalent
> > > > to ->read_iter, except that it will be called with the i_rwsem
> > > > held exclusively. Also the presence of ->integrity_read indicates
> > > > that the file system can support IMA.
> > > >
> > > > Signed-off-by: Christoph Hellwig <hch@lst.de>
> > >
> > > Fixes an IMA+XFS deadlock I've been seeing.
> >
> > Are you going to pick this up? Any feedback from the folks on the
> > LSM list on what additional file systems need to be wired up?
>
> That would normally come in via Mimi's tree, but I will pick it up if it
> doesn't.
With just this patch, a number of file measurements and appraisal
verifications are missing. I'm hoping to have an initial patch set
ready to be posted later this week.
Sorry for the delay.
Mimi
next prev parent reply other threads:[~2017-06-05 1:57 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 6:45 fix IMA deadlock Christoph Hellwig
2017-05-10 6:45 ` Christoph Hellwig
2017-05-10 6:45 ` [PATCH] security/ima: use fs method to read integrity data Christoph Hellwig
2017-05-10 6:45 ` Christoph Hellwig
2017-05-10 12:20 ` Boaz Harrosh
2017-05-10 12:20 ` Boaz Harrosh
2017-05-10 13:24 ` Christoph Hellwig
2017-05-10 13:24 ` Christoph Hellwig
2017-05-10 15:55 ` Boaz Harrosh
2017-05-10 15:55 ` Boaz Harrosh
2017-05-10 21:00 ` Mimi Zohar
2017-05-10 21:00 ` Mimi Zohar
2017-05-11 8:16 ` Christoph Hellwig
2017-05-11 8:16 ` Christoph Hellwig
2017-05-12 21:09 ` Mimi Zohar
2017-05-12 21:09 ` Mimi Zohar
2017-05-10 23:59 ` James Morris
2017-05-10 23:59 ` James Morris
2017-06-04 5:47 ` Christoph Hellwig
2017-06-04 5:47 ` Christoph Hellwig
2017-06-05 0:23 ` James Morris
2017-06-05 0:23 ` James Morris
2017-06-05 1:57 ` Mimi Zohar [this message]
2017-06-05 1:57 ` Mimi Zohar
2017-05-11 0:34 ` Li Kun
2017-05-11 0:34 ` Li Kun
2017-05-11 0:59 ` Al Viro
2017-05-11 0:59 ` Al Viro
2017-05-11 4:03 ` Li Kun
2017-05-11 4:03 ` Li Kun
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=1496627841.2998.44.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-security-module@vger.kernel.org \
/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.