From: Mimi Zohar <zohar@linux.ibm.com>
To: linux-unionfs@vger.kernel.org
Cc: linux-integrity@vger.kernel.org, linux-kernel@vger.kernel.org,
Amir Goldstein <amir73il@gmail.com>,
Christian Brauner <brauner@kernel.org>,
Seth Forshee <sforshee@kernel.org>,
Roberto Sassu <roberto.sassu@huaweicloud.com>
Subject: Re: [PATCH v2 2/3] evm: add support to disable EVM on unsupported filesystems
Date: Tue, 19 Dec 2023 14:09:58 -0500 [thread overview]
Message-ID: <ddff6449a57ef38e503fcaef759fa37ed391d134.camel@linux.ibm.com> (raw)
In-Reply-To: <20231219175206.12342-3-zohar@linux.ibm.com>
On Tue, 2023-12-19 at 12:52 -0500, Mimi Zohar wrote:
> diff --git a/include/linux/fs.h b/include/linux/fs.h
> index 98b7a7a8c42e..db9350a734ef 100644
> --- a/include/linux/fs.h
> +++ b/include/linux/fs.h
> @@ -1164,6 +1164,7 @@ extern int send_sigurg(struct fown_struct *fown);
> #define SB_I_USERNS_VISIBLE 0x00000010 /* fstype already mounted */
> #define SB_I_IMA_UNVERIFIABLE_SIGNATURE 0x00000020
> #define SB_I_UNTRUSTED_MOUNTER 0x00000040
> +#define SB_I_EVM_UNSUPPORTED 0x00000050
This needs to be fixed.
Mimi
>
> #define SB_I_SKIP_SYNC 0x00000100 /* Skip superblock at global sync */
> #define SB_I_PERSB_BDI 0x00000200 /* has a per-sb bdi */
> diff --git a/security/integrity/evm/evm_main.c b/security/integrity/evm/evm_main.c
next prev parent reply other threads:[~2023-12-19 19:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-19 17:52 [PATCH v2 0/3] evm: disable EVM on overlayfs Mimi Zohar
2023-12-19 17:52 ` [PATCH v2 1/3] evm: don't copy up 'security.evm' xattr Mimi Zohar
2023-12-19 17:52 ` [PATCH v2 2/3] evm: add support to disable EVM on unsupported filesystems Mimi Zohar
2023-12-19 19:09 ` Mimi Zohar [this message]
2023-12-20 4:23 ` Amir Goldstein
2023-12-19 17:52 ` [PATCH v2 3/3] overlay: disable EVM Mimi Zohar
2023-12-20 4:21 ` Amir Goldstein
2023-12-20 12:35 ` [PATCH v2 0/3] evm: disable EVM on overlayfs Christian Brauner
2023-12-20 14:19 ` 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=ddff6449a57ef38e503fcaef759fa37ed391d134.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=amir73il@gmail.com \
--cc=brauner@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-unionfs@vger.kernel.org \
--cc=roberto.sassu@huaweicloud.com \
--cc=sforshee@kernel.org \
/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