From: cpebenito@tresys.com (Christopher J. PeBenito)
To: refpolicy@oss.tresys.com
Subject: [refpolicy] resotorecon/setfiles generating avc: denied { getattr } on pseudo filesystems
Date: Tue, 4 Mar 2014 11:31:28 -0500 [thread overview]
Message-ID: <5315FFE0.7010009@tresys.com> (raw)
In-Reply-To: <20140304171237.41758378@soldur.bigon.be>
On 03/04/2014 11:12 AM, Laurent Bigonville wrote:
> Currently if you are running restorecon/fixfiles on a pseudo
> filesystem (sysfs_t, device_t, tmpfs_t) we are getting the following
> kind of AVC:
>
> type=AVC msg=audit(1393898218.762:236): avc: denied { getattr } for pid=3902 comm="setfiles" name="/" dev=tmpfs ino=5056 scontext=unconfined_u:unconfined_r:setfiles_t:s0-s0:c0.c1023 tcontext=system_u:object_r:tmpfs_t:s0 tclass=filesystem
> type=SYSCALL msg=audit(1393898218.762:236): arch=c000003e syscall=137 success=yes exit=0 a0=7f74fdd8d296 a1=7fffe0d11a70 a2=7f74fdd8d296 a3=6f6d2c6b38323032 items=0 ppid=3900 pid=3902 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts1 ses=4294967295 comm="setfiles" exe="/sbin/setfiles" subj=unconfined_u:unconfined_r:setfiles_t:s0-s0:c0.c1023 key=(null)
>
> This is happening because these file systems are not of the type fs_t.
> However these pseudo fs are supporting xattrs.
>
> Talking a bit with Dominick, he proposed to create a new
> "xattrfs" attribute attach it to all the filesystems and then use it
> instead of fs_t in the allow rules. This should probably also
> simplify/fix situations where files are moved around these pseudo-fs
> and real fs.
It sounds reasonable to me, now that fs_t is not the only xattr fs.
--
Chris PeBenito
Tresys Technology, LLC
www.tresys.com | oss.tresys.com
next prev parent reply other threads:[~2014-03-04 16:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-04 16:12 [refpolicy] resotorecon/setfiles generating avc: denied { getattr } on pseudo filesystems Laurent Bigonville
2014-03-04 16:31 ` Christopher J. PeBenito [this message]
2014-03-04 23:28 ` Laurent Bigonville
2014-03-05 17:36 ` Christopher J. 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=5315FFE0.7010009@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.