From: Ignaz Forster <iforster@suse.com>
To: Mimi Zohar <zohar@linux.ibm.com>,
linux-integrity@vger.kernel.org,
Miklos Szeredi <miklos@szeredi.hu>,
linux-unionfs@vger.kernel.org
Cc: Fabian Vogt <fvogt@suse.com>, Ignaz Forster <iforster@suse.de>
Subject: [RFC PATCH 0/5] Fix overlayfs on EVM
Date: Mon, 11 Feb 2019 17:53:18 +0100 [thread overview]
Message-ID: <20190211165323.9369-1-iforster@suse.com> (raw)
From: Ignaz Forster <iforster@suse.de>
This patch series tries to solve several problems found when using
EVM on an overlay file system.
Especially patch 4 and 5 will need further discussion; patch 4 will
introduce follow up problems, patch 5 can be considered a workaround
at best.
Ignaz Forster (4):
Rename ima_post_create_tmpfile
Execute IMA post create hook in vfs_create
Ignore IMA / EVM xattrs during copy_up
Use __vfs_getxattr to get overlayfs xattrs
Mimi Zohar (1):
evm: instead of using the overlayfs i_ino, use the real i_ino
fs/namei.c | 6 ++++--
fs/overlayfs/inode.c | 3 ++-
include/linux/ima.h | 4 ++--
security/integrity/evm/evm_crypto.c | 3 +++
security/integrity/evm/evm_main.c | 23 +++++++++++++++++++++++
security/integrity/ima/ima_main.c | 10 +++++-----
6 files changed, 39 insertions(+), 10 deletions(-)
--
2.20.1
next reply other threads:[~2019-02-11 16:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 16:53 Ignaz Forster [this message]
2019-02-11 16:53 ` [PATCH 1/5] evm: instead of using the overlayfs i_ino, use the real i_ino Ignaz Forster
2019-02-11 16:53 ` [PATCH 2/5] Rename ima_post_create_tmpfile Ignaz Forster
2019-02-11 16:53 ` [PATCH 3/5] Execute IMA post create hook in vfs_create Ignaz Forster
2019-02-11 16:53 ` [PATCH 4/5] Ignore IMA / EVM xattrs during copy_up Ignaz Forster
2019-02-12 2:55 ` Amir Goldstein
2019-02-11 16:53 ` [PATCH 5/5] Use __vfs_getxattr to get overlayfs xattrs Ignaz Forster
2019-02-12 3:29 ` [RFC PATCH 0/5] Fix overlayfs on EVM Amir Goldstein
2019-02-12 10:55 ` Fabian Vogt
2019-02-12 13:47 ` Amir Goldstein
2019-02-12 22:51 ` Mimi Zohar
2019-02-13 8:05 ` Fabian Vogt
2019-02-13 9:13 ` Amir Goldstein
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=20190211165323.9369-1-iforster@suse.com \
--to=iforster@suse.com \
--cc=fvogt@suse.com \
--cc=iforster@suse.de \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=zohar@linux.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 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).