From: "Christopher J. PeBenito" <cpebenito@tresys.com>
To: Stephen Smalley <sds@tycho.nsa.gov>
Cc: Daniel J Walsh <dwalsh@redhat.com>,
Eric Paris <eparis@redhat.com>, James Morris <jmorris@redhat.com>,
SE Linux <selinux@tycho.nsa.gov>
Subject: Re: Any idea why /proc/mtrr is marked as mtrr_device_t?
Date: Tue, 01 Aug 2006 10:01:46 -0400 [thread overview]
Message-ID: <1154440906.31522.100.camel@sgc> (raw)
In-Reply-To: <1154440486.3582.98.camel@moss-spartans.epoch.ncsc.mil>
On Tue, 2006-08-01 at 09:54 -0400, Stephen Smalley wrote:
> On Tue, 2006-08-01 at 09:42 -0400, Daniel J Walsh wrote:
> > Stephen Smalley wrote:
> > > See Documentation/mtrr.txt in the kernel tree.
> > >
> > >
> > So labeling a file as a device_t is ok?
> >
> > In strict policy xserver wants to write to it
>
> Yes, X needs access to it, and that rule existed in the old example
> policy. Does refpolicy lack it?
Looks like a bug in the interface. Xserver has dev_rw_mtrr(), but the
interface had mtrr_device_t:chr_file perms but was missing access for
the file class.
--
Chris PeBenito
Tresys Technology, LLC
(410) 290-1411 x150
--
This message was distributed to subscribers of the selinux mailing list.
If you no longer wish to subscribe, send mail to majordomo@tycho.nsa.gov with
the words "unsubscribe selinux" without quotes as the message.
prev parent reply other threads:[~2006-08-01 14:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 13:19 Any idea why /proc/mtrr is marked as mtrr_device_t? Daniel J Walsh
2006-08-01 13:28 ` Stephen Smalley
2006-08-01 13:42 ` Daniel J Walsh
2006-08-01 13:54 ` Stephen Smalley
2006-08-01 14:01 ` Christopher J. 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=1154440906.31522.100.camel@sgc \
--to=cpebenito@tresys.com \
--cc=dwalsh@redhat.com \
--cc=eparis@redhat.com \
--cc=jmorris@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@tycho.nsa.gov \
/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.