From: Dongsu Park <dongsu@kinvolk.io>
To: 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>,
Dongsu Park <dongsu@kinvolk.io>,
Miklos Szeredi <mszeredi@redhat.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Mimi Zohar <zohar@linux.vnet.ibm.com>,
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: [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE
Date: Tue, 30 Jan 2018 19:06:30 +0100 [thread overview]
Message-ID: <cover.1517314847.git.dongsu@kinvolk.io> (raw)
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.
There was a previous attempt (unmerged) with a IMA option named "force" and using
that option for FUSE filesystems. These patches use a different approach
so that the IMA subsystem does not need to know about FUSE.
- https://www.spinics.net/lists/linux-integrity/msg00948.html
- https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1584131.html
Changes since v1: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1587390.html
- include linux-fsdevel mailing list in cc
- mark patch as RFC
- based on next-integrity, without other unmerged FUSE / IMA patches
Changes since v2: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1587678.html
- rename flag to FS_IMA_NO_CACHE
- split patch into 2
Changes since v3: https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1592393.html
- make the code simpler by resetting IMA_DONE_MASK
The patchset is also available in our github repo:
https://github.com/kinvolk/linux/tree/dongsu/fuse-flag-ima-nocache-v4
Alban Crequy (2):
fuse: introduce new fs_type flag FS_IMA_NO_CACHE
ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE
fs/fuse/inode.c | 2 +-
include/linux/fs.h | 1 +
security/integrity/ima/ima_main.c | 15 +++++++++++++--
3 files changed, 15 insertions(+), 3 deletions(-)
--
2.13.6
WARNING: multiple messages have this Message-ID (diff)
From: dongsu@kinvolk.io (Dongsu Park)
To: linux-security-module@vger.kernel.org
Subject: [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE
Date: Tue, 30 Jan 2018 19:06:30 +0100 [thread overview]
Message-ID: <cover.1517314847.git.dongsu@kinvolk.io> (raw)
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.
There was a previous attempt (unmerged) with a IMA option named "force" and using
that option for FUSE filesystems. These patches use a different approach
so that the IMA subsystem does not need to know about FUSE.
- https://www.spinics.net/lists/linux-integrity/msg00948.html
- https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1584131.html
Changes since v1: https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1587390.html
- include linux-fsdevel mailing list in cc
- mark patch as RFC
- based on next-integrity, without other unmerged FUSE / IMA patches
Changes since v2: https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1587678.html
- rename flag to FS_IMA_NO_CACHE
- split patch into 2
Changes since v3: https://www.mail-archive.com/linux-kernel at vger.kernel.org/msg1592393.html
- make the code simpler by resetting IMA_DONE_MASK
The patchset is also available in our github repo:
https://github.com/kinvolk/linux/tree/dongsu/fuse-flag-ima-nocache-v4
Alban Crequy (2):
fuse: introduce new fs_type flag FS_IMA_NO_CACHE
ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE
fs/fuse/inode.c | 2 +-
include/linux/fs.h | 1 +
security/integrity/ima/ima_main.c | 15 +++++++++++++--
3 files changed, 15 insertions(+), 3 deletions(-)
--
2.13.6
--
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 reply other threads:[~2018-01-30 18:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 18:06 Dongsu Park [this message]
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 ` [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 ` [RFC PATCH v4 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE Mimi Zohar
2018-02-01 18:36 ` 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.1517314847.git.dongsu@kinvolk.io \
--to=dongsu@kinvolk.io \
--cc=alban@kinvolk.io \
--cc=dmitry.kasatkin@gmail.com \
--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 \
--cc=zohar@linux.vnet.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 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.