From: James Morris <jmorris@namei.org>
To: Eric Paris <eparis@redhat.com>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
Eric Paris <eparis@parisplace.org>,
selinux <selinux@tycho.nsa.gov>,
linux-security-module@vger.kernel.org, casey@schaufler-ca.com
Subject: Re: [patch] selinux: handle files opened with flags 3 by checking ioctl permission
Date: Tue, 18 Mar 2008 10:02:17 +1100 (EST) [thread overview]
Message-ID: <Xine.LNX.4.64.0803181000390.18000@us.intercode.com.au> (raw)
In-Reply-To: <1205792367.2891.1.camel@localhost.localdomain>
On Mon, 17 Mar 2008, Eric Paris wrote:
> > Fixes the problem I was seeing. Applied to for-akpm.
>
> Are you at least now seeing a FILE__IOCTL avc for mdadm? If not why
> would mdadm have that permission for /dev/null?
kernel: [ 4.779280] type=1400 audit(1205792724.308:4): avc: granted null
for pid=1792 comm="mdadm" name="null" dev=tmpfs ino=189
scontext=system_u:system_r:mdadm_t:s0
tcontext=system_u:object_r:null_device_t:s0 tclass=chr_file
Possibly related.
--
James Morris
<jmorris@namei.org>
--
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.
next prev parent reply other threads:[~2008-03-17 23:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 19:13 How to handle security_dentry_open when the open flags are 'special' Eric Paris
2008-03-12 19:20 ` Eric Paris
2008-03-13 11:56 ` Stephen Smalley
2008-03-14 14:16 ` Stephen Smalley
2008-03-16 21:41 ` James Morris
2008-03-17 12:55 ` [patch] selinux: handle files opened with flags 3 by checking ioctl permission Stephen Smalley
2008-03-17 14:01 ` Eric Paris
2008-03-17 14:19 ` Stephen Smalley
2008-03-17 14:30 ` Eric Paris
2008-03-17 22:15 ` James Morris
2008-03-17 22:19 ` Eric Paris
2008-03-17 23:02 ` James Morris [this message]
2008-03-18 12:54 ` Stephen Smalley
2008-03-18 12:52 ` Stephen Smalley
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=Xine.LNX.4.64.0803181000390.18000@us.intercode.com.au \
--to=jmorris@namei.org \
--cc=casey@schaufler-ca.com \
--cc=eparis@parisplace.org \
--cc=eparis@redhat.com \
--cc=linux-security-module@vger.kernel.org \
--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.