From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] [PATCH 3/4] Allow mount_t usage of /dev/loop-control
Date: Sat, 8 Feb 2014 10:51:15 -0500 [thread overview]
Message-ID: <52F65273.6000608@tresys.com> (raw)
In-Reply-To: <1391262624-4486-4-git-send-email-aranea@aixah.de>
On 2/1/2014 8:50 AM, Luis Ressel wrote:
> If loopback devices are not pregenerated (kernel option
> CONFIG_BLK_DEV_LOOP_MIN_COUNT=0), mount needs to write to
> /dev/loop-control do create them dynamically when needed.
> ---
> policy/modules/system/mount.te | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/policy/modules/system/mount.te b/policy/modules/system/mount.te
> index 9cd37d9..90c928b 100644
> --- a/policy/modules/system/mount.te
> +++ b/policy/modules/system/mount.te
> @@ -77,6 +77,7 @@ dev_list_all_dev_nodes(mount_t)
> dev_read_sysfs(mount_t)
> dev_dontaudit_write_sysfs_dirs(mount_t)
> dev_rw_lvm_control(mount_t)
> +dev_rw_loop_control(mount_t)
> dev_dontaudit_getattr_all_chr_files(mount_t)
> dev_dontaudit_getattr_memory_dev(mount_t)
> dev_getattr_sound_dev(mount_t)
Merged.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-02-08 15:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-01 13:50 [refpolicy] Updated loopback mount patches Luis Ressel
2014-02-01 13:50 ` [refpolicy] [PATCH 1/4] kernel/devices.if: Add dev_rw_loop_control interface Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 13:50 ` [refpolicy] [PATCH 2/4] system/mount.if: Add mount_read_mount_loopback interface Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 13:50 ` [refpolicy] [PATCH 3/4] Allow mount_t usage of /dev/loop-control Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito [this message]
2014-02-01 13:50 ` [refpolicy] [PATCH 4/4] Grant kernel_t necessary permissions for loopback mounts Luis Ressel
2014-02-08 15:51 ` Christopher J. PeBenito
2014-02-01 14:32 ` [refpolicy] Updated loopback mount patches Luis Ressel
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=52F65273.6000608@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.