From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH v2 2/3] Associate the new xattrfs attribute to fs_t and some pseudo-fs
Date: Fri, 4 Apr 2014 15:50:21 -0400 [thread overview]
Message-ID: <533F0CFD.2090009@tresys.com> (raw)
In-Reply-To: <20140324144706.52b5f1e0@soldur.bigon.be>
On 03/24/2014 09:47 AM, Laurent Bigonville wrote:
> Le Sat, 22 Mar 2014 13:06:10 +0100,
> Laurent Bigonville <bigon@debian.org> a ?crit :
>
> [...]
>> b/policy/modules/kernel/filesystem.te index 4207e8f..a8a54d2 100644
>> --- a/policy/modules/kernel/filesystem.te
>> +++ b/policy/modules/kernel/filesystem.te
>> @@ -17,6 +17,7 @@ attribute xattrfs;
>> #
>> type fs_t;
>> fs_type(fs_t)
>> +typeattribute fs_t xattrfs;
>> sid fs gen_context(system_u:object_r:fs_t,s0)
>>
>> # Use xattrs for the following filesystem types.
>
> This should probably be changed to use the new fs_xattr_type() of
> course, or set the attribute directly as it's local.
>
> [...]
>
> I can post a v3 of the patch if you want
I'd prefer to keep consistent and use a fs_xattr_type() call.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-04-04 19:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-22 12:06 [refpolicy] [PATCH v2 1/3] Create new xattrfs attribute and fs_getattr_all_xattr_fs() interface Laurent Bigonville
2014-03-22 12:06 ` [refpolicy] [PATCH v2 2/3] Associate the new xattrfs attribute to fs_t and some pseudo-fs Laurent Bigonville
2014-03-24 13:47 ` Laurent Bigonville
2014-04-04 19:50 ` Christopher J. PeBenito [this message]
2014-03-22 12:06 ` [refpolicy] [PATCH v2 3/3] Use new fs_getattr_all_xattr_fs interface for setfiles_t and restorecond_t Laurent Bigonville
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=533F0CFD.2090009@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.