From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Dongsu Park <dongsu@kinvolk.io>, linux-kernel@vger.kernel.org
Cc: linux-integrity@vger.kernel.org,
linux-security-module@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Alban Crequy <alban@kinvolk.io>,
Miklos Szeredi <mszeredi@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Dmitry Kasatkin <dmitry.kasatkin@gmail.com>,
James Morris <jmorris@namei.org>,
Christoph Hellwig <hch@infradead.org>,
"Serge E . Hallyn" <serge@hallyn.com>,
Seth Forshee <seth.forshee@canonical.com>
Subject: Re: [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE
Date: Thu, 01 Feb 2018 13:36:53 -0500 [thread overview]
Message-ID: <1517510213.6675.12.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1517314847.git.dongsu@kinvolk.io>
On Tue, 2018-01-30 at 19:06 +0100, Dongsu Park wrote:
> This patchset v4 introduces a new fs flag FS_IMA_NO_CACHE and uses it in
> FUSE. This forces files to be re-measured, re-appraised and re-audited
> on file systems with the feature flag FS_IMA_NO_CACHE. In that way,
> cached integrity results won't be used.
Thanks!
Mimi
WARNING: multiple messages have this Message-ID (diff)
From: zohar@linux.vnet.ibm.com (Mimi Zohar)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE
Date: Thu, 01 Feb 2018 13:36:53 -0500 [thread overview]
Message-ID: <1517510213.6675.12.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <cover.1517314847.git.dongsu@kinvolk.io>
On Tue, 2018-01-30 at 19:06 +0100, Dongsu Park wrote:
> This patchset v4 introduces a new fs flag FS_IMA_NO_CACHE and uses it in
> FUSE. This forces files to be re-measured, re-appraised and re-audited
> on file systems with the feature flag FS_IMA_NO_CACHE. In that way,
> cached integrity results won't be used.
Thanks!
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
next prev parent reply other threads:[~2018-02-01 18:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:06 [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE Dongsu Park
2018-01-30 18:06 ` Dongsu Park
2018-01-30 18:06 ` [RFC PATCH v4 1/2] fuse: introduce new fs_type " Dongsu Park
2018-01-30 18:06 ` Dongsu Park
2018-02-02 15:20 ` Mimi Zohar
2018-02-02 15:20 ` Mimi Zohar
2018-02-02 15:20 ` Mimi Zohar
2018-02-02 15:33 ` Mimi Zohar
2018-02-02 15:33 ` Mimi Zohar
2018-02-02 15:33 ` Mimi Zohar
2018-02-02 16:10 ` Miklos Szeredi
2018-02-02 16:10 ` Miklos Szeredi
2018-02-02 16:59 ` Mimi Zohar
2018-02-02 16:59 ` Mimi Zohar
2018-02-02 16:59 ` Mimi Zohar
2018-02-05 14:16 ` Alban Crequy
2018-02-05 14:16 ` Alban Crequy
2018-02-07 9:21 ` Miklos Szeredi
2018-02-07 9:21 ` Miklos Szeredi
2018-02-07 13:05 ` Mimi Zohar
2018-02-07 13:05 ` Mimi Zohar
2018-01-30 18:06 ` [RFC PATCH v4 2/2] ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE Dongsu Park
2018-01-30 18:06 ` Dongsu Park
2018-02-01 18:36 ` Mimi Zohar [this message]
2018-02-01 18:36 ` [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE 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=1517510213.6675.12.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=alban@kinvolk.io \
--cc=dmitry.kasatkin@gmail.com \
--cc=dongsu@kinvolk.io \
--cc=hch@infradead.org \
--cc=jmorris@namei.org \
--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=mszeredi@redhat.com \
--cc=serge@hallyn.com \
--cc=seth.forshee@canonical.com \
--cc=viro@zeniv.linux.org.uk \
/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.