From: Mimi Zohar <zohar@linux.vnet.ibm.com>
To: Sascha Hauer <s.hauer@pengutronix.de>, linux-integrity@vger.kernel.org
Cc: Matthew Garrett <mjg59@google.com>
Subject: Re: [PATCH] evm: check for remount ro in progress before writing
Date: Thu, 08 Mar 2018 16:42:27 -0500 [thread overview]
Message-ID: <1520545347.3605.107.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <20180301123845.26189-1-s.hauer@pengutronix.de>
On Thu, 2018-03-01 at 13:38 +0100, Sascha Hauer wrote:
> EVM might update the evm xattr while the VFS performs a remount to
> readonly mode. This is not properly checked for, additionally check
> the s_readonly_remount superblock flag before writing.
> The bug can for example be observed with UBIFS. UBIFS checks the free
> space on the device before and after a remount. With EVM enabled the
> free space sometimes differs between both checks.
>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> ---
> security/integrity/evm/evm_main.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/security/integrity/evm/evm_main.c b/security/integrity/evm/evm_main.c
> index a8d502827270..4a147a998aa7 100644
> --- a/security/integrity/evm/evm_main.c
> +++ b/security/integrity/evm/evm_main.c
> @@ -185,6 +185,7 @@ static enum integrity_status evm_verify_hmac(struct dentry *dentry,
> iint->flags |= EVM_IMMUTABLE_DIGSIG;
> evm_status = INTEGRITY_PASS_IMMUTABLE;
> } else if (!IS_RDONLY(d_backing_inode(dentry)) &&
> + !(dentry->d_inode->i_sb->s_readonly_remount) &&
> !IS_IMMUTABLE(d_backing_inode(dentry))) {
> evm_update_evmxattr(dentry, xattr_name,
> xattr_value,
Mathew's EVM Portable signature patch should have inverted the (!rc)
test, but didn't. With this patch, there's now a checkpatch over 80
character line warning.
Mimi
next prev parent reply other threads:[~2018-03-08 21:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 12:38 [PATCH] evm: check for remount ro in progress before writing Sascha Hauer
2018-03-08 21:42 ` Mimi Zohar [this message]
2018-03-11 21:52 ` Mimi Zohar
2018-03-16 17:12 ` 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=1520545347.3605.107.camel@linux.vnet.ibm.com \
--to=zohar@linux.vnet.ibm.com \
--cc=linux-integrity@vger.kernel.org \
--cc=mjg59@google.com \
--cc=s.hauer@pengutronix.de \
/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.