From: Alban Crequy <alban.crequy@gmail.com> To: alban@kinvolk.io Cc: dongsu@kinvolk.io, iago@kinvolk.io, linux-kernel@vger.kernel.org, linux-integrity@vger.kernel.org, linux-security-module@vger.kernel.org, linux-fsdevel@vger.kernel.org, miklos@szeredi.hu, viro@zeniv.linux.org.uk, zohar@linux.vnet.ibm.com, dmitry.kasatkin@gmail.com, james.l.morris@oracle.com, serge@hallyn.com, seth.forshee@canonical.com, hch@infradead.org Subject: [RFC PATCH v3 1/2] fuse: introduce new fs_type flag FS_IMA_NO_CACHE Date: Mon, 22 Jan 2018 17:24:51 +0100 [thread overview] Message-ID: <20180122162452.8756-2-alban@kinvolk.io> (raw) In-Reply-To: <20180122162452.8756-1-alban@kinvolk.io> From: Alban Crequy <alban@kinvolk.io> This new fs_type flag FS_IMA_NO_CACHE means files should be re-measured, re-appraised and re-audited each time. Cached integrity results should not be used. It is useful in FUSE because the userspace FUSE process can change the underlying files at any time without notifying the kernel. Cc: linux-kernel@vger.kernel.org Cc: linux-integrity@vger.kernel.org Cc: linux-security-module@vger.kernel.org Cc: linux-fsdevel@vger.kernel.org Cc: Miklos Szeredi <miklos@szeredi.hu> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: Mimi Zohar <zohar@linux.vnet.ibm.com> Cc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com> Cc: James Morris <james.l.morris@oracle.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Seth Forshee <seth.forshee@canonical.com> Cc: Christoph Hellwig <hch@infradead.org> Tested-by: Dongsu Park <dongsu@kinvolk.io> Signed-off-by: Alban Crequy <alban@kinvolk.io> --- fs/fuse/inode.c | 2 +- include/linux/fs.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c index 624f18bbfd2b..0a9e516461d5 100644 --- a/fs/fuse/inode.c +++ b/fs/fuse/inode.c @@ -1205,7 +1205,7 @@ static void fuse_kill_sb_anon(struct super_block *sb) static struct file_system_type fuse_fs_type = { .owner = THIS_MODULE, .name = "fuse", - .fs_flags = FS_HAS_SUBTYPE, + .fs_flags = FS_HAS_SUBTYPE | FS_IMA_NO_CACHE, .mount = fuse_mount, .kill_sb = fuse_kill_sb_anon, }; diff --git a/include/linux/fs.h b/include/linux/fs.h index 511fbaabf624..ced841ba6701 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -2075,6 +2075,7 @@ struct file_system_type { #define FS_BINARY_MOUNTDATA 2 #define FS_HAS_SUBTYPE 4 #define FS_USERNS_MOUNT 8 /* Can be mounted by userns root */ +#define FS_IMA_NO_CACHE 16 /* Force IMA to re-measure, re-appraise, re-audit files */ #define FS_RENAME_DOES_D_MOVE 32768 /* FS will handle d_move() during rename() internally. */ struct dentry *(*mount) (struct file_system_type *, int, const char *, void *); -- 2.13.6
WARNING: multiple messages have this Message-ID (diff)
From: alban.crequy@gmail.com (Alban Crequy) To: linux-security-module@vger.kernel.org Subject: [RFC PATCH v3 1/2] fuse: introduce new fs_type flag FS_IMA_NO_CACHE Date: Mon, 22 Jan 2018 17:24:51 +0100 [thread overview] Message-ID: <20180122162452.8756-2-alban@kinvolk.io> (raw) In-Reply-To: <20180122162452.8756-1-alban@kinvolk.io> From: Alban Crequy <alban@kinvolk.io> This new fs_type flag FS_IMA_NO_CACHE means files should be re-measured, re-appraised and re-audited each time. Cached integrity results should not be used. It is useful in FUSE because the userspace FUSE process can change the underlying files at any time without notifying the kernel. Cc: linux-kernel at vger.kernel.org Cc: linux-integrity at vger.kernel.org Cc: linux-security-module at vger.kernel.org Cc: linux-fsdevel at vger.kernel.org Cc: Miklos Szeredi <miklos@szeredi.hu> Cc: Alexander Viro <viro@zeniv.linux.org.uk> Cc: Mimi Zohar <zohar@linux.vnet.ibm.com> Cc: Dmitry Kasatkin <dmitry.kasatkin@gmail.com> Cc: James Morris <james.l.morris@oracle.com> Cc: "Serge E. Hallyn" <serge@hallyn.com> Cc: Seth Forshee <seth.forshee@canonical.com> Cc: Christoph Hellwig <hch@infradead.org> Tested-by: Dongsu Park <dongsu@kinvolk.io> Signed-off-by: Alban Crequy <alban@kinvolk.io> --- fs/fuse/inode.c | 2 +- include/linux/fs.h | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/fs/fuse/inode.c b/fs/fuse/inode.c index 624f18bbfd2b..0a9e516461d5 100644 --- a/fs/fuse/inode.c +++ b/fs/fuse/inode.c @@ -1205,7 +1205,7 @@ static void fuse_kill_sb_anon(struct super_block *sb) static struct file_system_type fuse_fs_type = { .owner = THIS_MODULE, .name = "fuse", - .fs_flags = FS_HAS_SUBTYPE, + .fs_flags = FS_HAS_SUBTYPE | FS_IMA_NO_CACHE, .mount = fuse_mount, .kill_sb = fuse_kill_sb_anon, }; diff --git a/include/linux/fs.h b/include/linux/fs.h index 511fbaabf624..ced841ba6701 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -2075,6 +2075,7 @@ struct file_system_type { #define FS_BINARY_MOUNTDATA 2 #define FS_HAS_SUBTYPE 4 #define FS_USERNS_MOUNT 8 /* Can be mounted by userns root */ +#define FS_IMA_NO_CACHE 16 /* Force IMA to re-measure, re-appraise, re-audit files */ #define FS_RENAME_DOES_D_MOVE 32768 /* FS will handle d_move() during rename() internally. */ struct dentry *(*mount) (struct file_system_type *, int, const char *, void *); -- 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 prev parent reply other threads:[~2018-01-22 16:25 UTC|newest] Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-01-22 16:24 [RFC PATCH v3 0/2] ima,fuse: introduce new fs flag FS_IMA_NO_CACHE Alban Crequy 2018-01-22 16:24 ` Alban Crequy 2018-01-22 16:24 ` Alban Crequy [this message] 2018-01-22 16:24 ` [RFC PATCH v3 1/2] fuse: introduce new fs_type " Alban Crequy 2018-01-22 16:24 ` [RFC PATCH v3 2/2] ima: force re-appraisal on filesystems with FS_IMA_NO_CACHE Alban Crequy 2018-01-22 16:24 ` Alban Crequy 2018-01-22 22:24 ` Seth Forshee 2018-01-22 22:24 ` Seth Forshee 2018-01-24 17:53 ` Serge E. Hallyn 2018-01-24 17:53 ` Serge E. Hallyn 2018-01-24 17:52 ` Serge E. Hallyn 2018-01-24 17:52 ` Serge E. Hallyn 2018-01-25 11:56 ` Mimi Zohar 2018-01-25 11:56 ` Mimi Zohar 2018-01-25 11:56 ` Mimi Zohar 2018-01-29 16:33 ` Mimi Zohar 2018-01-29 16:33 ` Mimi Zohar 2018-01-29 16:33 ` Mimi Zohar 2018-01-29 17:40 ` Dongsu Park 2018-01-29 17:40 ` Dongsu Park 2018-01-30 18:13 ` Dongsu Park 2018-01-30 18:13 ` Dongsu Park
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=20180122162452.8756-2-alban@kinvolk.io \ --to=alban.crequy@gmail.com \ --cc=alban@kinvolk.io \ --cc=dmitry.kasatkin@gmail.com \ --cc=dongsu@kinvolk.io \ --cc=hch@infradead.org \ --cc=iago@kinvolk.io \ --cc=james.l.morris@oracle.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=miklos@szeredi.hu \ --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: linkBe 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.