From: Amir Goldstein <amir73il@gmail.com>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: linux-unionfs@vger.kernel.org, linux-integrity@vger.kernel.org,
linux-kernel@vger.kernel.org,
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: Wed, 20 Dec 2023 06:23:49 +0200 [thread overview]
Message-ID: <CAOQ4uxgn3X5Py9XE6wmafPpUBSXDzygUpgDSVct9AfzH+0kvXA@mail.gmail.com> (raw)
In-Reply-To: <ddff6449a57ef38e503fcaef759fa37ed391d134.camel@linux.ibm.com>
On Tue, Dec 19, 2023 at 9:10 PM Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> 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.
>
With this fixed, you may add:
Acked-by: Amir Goldstein <amir73il@gmail.com>
Thanks,
Amir.
next prev parent reply other threads:[~2023-12-20 4:24 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
2023-12-20 4:23 ` Amir Goldstein [this message]
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=CAOQ4uxgn3X5Py9XE6wmafPpUBSXDzygUpgDSVct9AfzH+0kvXA@mail.gmail.com \
--to=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 \
--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 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.