From: Chris PeBenito <pebenito@ieee.org>
To: Gao Xiang <xiang@kernel.org>, selinux-refpolicy@vger.kernel.org
Cc: linux-erofs@lists.ozlabs.org, David Michael <fedora.dm0@gmail.com>
Subject: Re: [PATCH] Add erofs as a SELinux capable file system
Date: Tue, 5 Oct 2021 14:50:22 -0400 [thread overview]
Message-ID: <26267281-d183-6d5c-6490-57c7376625ab@ieee.org> (raw)
In-Reply-To: <20211004035901.5428-1-xiang@kernel.org>
On 10/3/21 11:59 PM, Gao Xiang wrote:
> EROFS supported the security xattr handler from Linux v4.19.
> Add erofs to the filesystem policy now.
>
> Reported-by: David Michael <fedora.dm0@gmail.com>
> Signed-off-by: Gao Xiang <xiang@kernel.org>
> ---
> policy/modules/kernel/filesystem.te | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/policy/modules/kernel/filesystem.te b/policy/modules/kernel/filesystem.te
> index 7282acba8537..8109348f70de 100644
> --- a/policy/modules/kernel/filesystem.te
> +++ b/policy/modules/kernel/filesystem.te
> @@ -24,6 +24,7 @@ sid fs gen_context(system_u:object_r:fs_t,s0)
> # Requires that a security xattr handler exist for the filesystem.
> fs_use_xattr btrfs gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr encfs gen_context(system_u:object_r:fs_t,s0);
> +fs_use_xattr erofs gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr ext2 gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr ext3 gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr ext4 gen_context(system_u:object_r:fs_t,s0);
Merged. Thanks!
--
Chris PeBenito
prev parent reply other threads:[~2021-10-05 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <8735pjoxbk.fsf@gmail.com>
2021-10-04 3:59 ` [PATCH] Add erofs as a SELinux capable file system Gao Xiang
2021-10-05 18:50 ` Chris PeBenito [this message]
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=26267281-d183-6d5c-6490-57c7376625ab@ieee.org \
--to=pebenito@ieee.org \
--cc=fedora.dm0@gmail.com \
--cc=linux-erofs@lists.ozlabs.org \
--cc=selinux-refpolicy@vger.kernel.org \
--cc=xiang@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).