All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Smalley <sds@tycho.nsa.gov>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: Eric Paris <eparis@parisplace.org>,
	James Morris <jmorris@namei.org>,
	qingtao.cao@windriver.com, selinux@tycho.nsa.gov
Subject: Re: [PATCH] selinux: Fix regression for Xorg
Date: Mon, 28 Mar 2011 10:24:39 -0400	[thread overview]
Message-ID: <1301322279.23818.19.camel@moss-pluto> (raw)
In-Reply-To: <1301316132.23818.7.camel@moss-pluto>

On Mon, 2011-03-28 at 08:42 -0400, Stephen Smalley wrote:
> On Fri, 2011-03-25 at 20:03 -0700, Justin P. Mattock wrote:
> > not sure whats going on now.. but loading up the latest on my iMac with 
> > the below patch makes no difference I still hit the bug macbook pro 
> > works fine(maybe something with the different video drivers or something)
> > 
> > full dmesg of my iMac here:
> > http://fpaste.org/SNFC/
> 
> Hi Justin,
> 
> I did before and after testing using the compute_create utility from
> libselinux/utils, and it showed that the kernel returned the wrong
> context prior to the patch and the right context afterward.  I'm
> guessing you aren't booting the right kernel or didn't apply the patch
> correctly.
> 
> You can run:
> compute_create `id -Z` `id -Z` x_drawable
> and see whether the returned context has object_r or not.

Also, I tested before and after the patch with Xorg, and confirmed that
the compute_sid errors vanished when using a kernel with the patch
applied.

-- 
Stephen Smalley
National Security Agency


--
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.

  reply	other threads:[~2011-03-28 14:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-21 16:52 SELinux: avc_has_perm: unexpected error 22 Justin P. Mattock
2011-03-21 16:52 ` [refpolicy] " Justin P. Mattock
2011-03-23 18:07 ` Justin P. Mattock
2011-03-23 18:07   ` [refpolicy] " Justin P. Mattock
2011-03-24  2:30   ` Justin P. Mattock
2011-03-24  2:30     ` [refpolicy] " Justin P. Mattock
2011-03-24 13:58     ` Stephen Smalley
2011-03-24 13:58       ` [refpolicy] " Stephen Smalley
2011-03-24 16:26       ` Justin P. Mattock
2011-03-24 16:26         ` [refpolicy] " Justin P. Mattock
2011-03-24 20:13         ` Stephen Smalley
2011-03-24 20:22           ` Justin P. Mattock
2011-03-24 20:24             ` Stephen Smalley
2011-03-24 20:43               ` Justin P. Mattock
2011-03-25  3:18                 ` Harry Ciao
2011-03-25 12:26                   ` Stephen Smalley
2011-03-25 12:34                     ` Stephen Smalley
2011-03-25 14:13                       ` [PATCH] selinux: Fix regression for Xorg Stephen Smalley
2011-03-25 18:04                         ` Justin P. Mattock
2011-03-26  3:03                         ` Justin P. Mattock
2011-03-28 12:42                           ` Stephen Smalley
2011-03-28 14:24                             ` Stephen Smalley [this message]
2011-03-28 16:20                               ` Justin P. Mattock
2011-03-28 22:28                               ` Justin P. Mattock

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=1301322279.23818.19.camel@moss-pluto \
    --to=sds@tycho.nsa.gov \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=justinmattock@gmail.com \
    --cc=qingtao.cao@windriver.com \
    --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.