From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH] Implement zfs support
Date: Wed, 28 Nov 2012 16:43:14 -0500 [thread overview]
Message-ID: <50B68572.1060006@tresys.com> (raw)
In-Reply-To: <50B4DC4E.2000108@mthode.org>
On 11/27/12 10:29, Matthew Thode wrote:
> Just adding zfs to the list of defined filesystems in filesystem.te
>
> Signed-off-by: Matthew Thode <mthode@mthode.org>
> ---
> policy/modules/kernel/filesystem.te
> 1 files changed, 1 insertions(+), 0 deletions (-)
>
> diff --git a/policy/modules/kernel/filesystem.te
> b/policy/modules/kernel/filesystem.te
> index 6bd38c8..e746ee5 100644
> --- a/policy/modules/kernel/filesystem.te
> +++ b/policy/modules/kernel/filesystem.te
> @@ -33,6 +33,7 @@ fs_use_xattr jffs2 gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr jfs gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr lustre gen_context(system_u:object_r:fs_t,s0);
> fs_use_xattr xfs gen_context(system_u:object_r:fs_t,s0);
> +fs_use_xattr zfs gen_context(system_u:object_r:fs_t,s0);
>
> # Use the allocating task SID to label inodes in the following filesystem
> # types, and label the filesystem itself with the specified context.
Is the security label support in the upstream ZFS on Linux repo?
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2012-11-28 21:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-27 15:29 [refpolicy] [PATCH] Implement zfs support Matthew Thode
2012-11-28 21:43 ` Christopher J. PeBenito [this message]
2012-11-28 22:06 ` Matthew Thode
2012-12-07 17:22 ` Matthew Thode
2012-12-07 18:26 ` Chris PeBenito
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=50B68572.1060006@tresys.com \
--to=cpebenito@tresys.com \
--cc=refpolicy@oss.tresys.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.