From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: "Darrick J. Wong" <darrick.wong@oracle.com>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>
Cc: linux-integrity <linux-integrity@vger.kernel.org>,
linux-security-module <linux-security-module@vger.kernel.org>,
Jan Kara <jack@suse.com>, "Theodore Ts'o" <tytso@mit.edu>,
Chris Mason <clm@fb.com>, Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Dmitry Kasatkin <dmitry.kasatkin@huawei.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCHv6 1/1] ima: re-introduce own integrity cache lock
Date: Tue, 02 Jan 2018 21:52:03 -0500 [thread overview]
Message-ID: <1514947923.3493.2.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180103014048.GE5146@magnolia>
On Tue, 2018-01-02 at 17:40 -0800, Darrick J. Wong wrote:
> [might as well cc linux-xfs]
>
> On Thu, Dec 14, 2017 at 12:22:37AM +0200, Dmitry Kasatkin wrote:
> > Hi,
> >
> > Could I ask FS maintainers to test IMA with this patch additionally
> > and provide ack/tested.
> > We tested but may be you have and some special testing.
>
> Super-late to this party, but unless xfstests has automated tests to
> set up IMA on top of an existing filesystem then I most likely have no
> idea /how/ to test IMA. I did a quick grep of xfstests git and I don't
> see anything IMA-related.
Back in June I posted a simple xfstests IMA-appraisal test (https://ma
rc.info/?l=linux-fsdevel&m=149703820814885&w=4).
Mimi
next prev parent reply other threads:[~2018-01-03 2:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-05 19:06 [PATCHv6 1/1] ima: re-introduce own integrity cache lock Dmitry Kasatkin
2017-12-13 22:22 ` Dmitry Kasatkin
2018-01-03 1:40 ` Darrick J. Wong
2018-01-03 2:52 ` Mimi Zohar [this message]
2018-01-03 3:16 ` Dave Chinner
2018-01-03 4:03 ` 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=1514947923.3493.2.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=clm@fb.com \
--cc=darrick.wong@oracle.com \
--cc=dmitry.kasatkin@gmail.com \
--cc=dmitry.kasatkin@huawei.com \
--cc=hch@infradead.org \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=linux-xfs@vger.kernel.org \
--cc=tytso@mit.edu \
/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).