All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominick Grift <domg472@gmail.com>
To: Eamon Walsh <ewalsh@tycho.nsa.gov>
Cc: Stephen Smalley <sds@tycho.nsa.gov>,
	SELinux@tycho.nsa.gov, Daniel J Walsh <dwalsh@redhat.com>
Subject: Re: avc: denied null
Date: Thu, 21 May 2009 14:19:52 +0200	[thread overview]
Message-ID: <1242908392.3001.8.camel@notebook2.grift.internal> (raw)
In-Reply-To: <4A14BE43.7070505@tycho.nsa.gov>

On Wed, 2009-05-20 at 22:36 -0400, Eamon Walsh wrote:

> If you're willing to compile the X server from source, you could apply
> the attached patch and use gdb to attach to the running X server (this
> has to be done over an ssh connection). 
> 
> Break on the SELinuxNullPermissionHappened function and reproduce the
> GLXMakeCurrent avc, hopefully the breakpoint will fire and you can get a
> backtrace.
> 
> Also there is another patch that will fix the x_device null avc's
> (attached).
> 
I tried this. The null avc denials occur on login. 

However, as soon as i "break SELinuxNullPermissionHappened", my login screen becomes unresponsive.

When i cancel the "break" it becomes responsive again.

As you can imagine it is difficult to reproduce the issue if this
happens, as i cannot log in (this is where the null avc occurs) with the
"breakpoint" set.

Any suggestions?

this is what i did:
- rebuild/reinstall xorg rpms with your patches included (seems to work
fine and the other null avcs are gone)
- installed xorg debuginfo rpm
- login using ssh and as root: gdb /usr/bin/Xorg <pid>
- break SELinuxNullPermissionHappened



--
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:[~2009-05-21 12:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-18 10:19 avc: denied null Dominick Grift
2009-05-18 12:50 ` Stephen Smalley
2009-05-18 12:59   ` Dominick Grift
2009-05-18 18:52     ` Eamon Walsh
2009-05-20  3:11     ` Eamon Walsh
2009-05-20  7:21       ` Policy loading problem Dennis Wronka
2009-05-20 11:46         ` Stephen Smalley
2009-05-20 13:46           ` Dennis Wronka
2009-05-20 13:49             ` Stephen Smalley
2009-05-20 14:07               ` Dennis Wronka
2009-05-20 14:09                 ` Stephen Smalley
2009-05-20 14:21                   ` Stephen Smalley
2009-05-20 14:42                     ` Dennis Wronka
2009-05-20 14:40                       ` Stephen Smalley
2009-05-20 14:57                         ` Dennis Wronka
2009-05-20 14:59                           ` Stephen Smalley
2009-05-20 15:22                             ` Dennis Wronka
2009-05-20 15:44                             ` Dennis Wronka
2009-05-20 16:44                               ` Stephen Smalley
2009-05-20 21:01                                 ` Paul Howarth
2009-05-20 15:10                           ` Stephen Smalley
2009-07-07 15:53                             ` Joshua Brindle
2009-05-20 11:08       ` avc: denied null Dominick Grift
2009-05-21  2:36         ` Eamon Walsh
2009-05-21 12:19           ` Dominick Grift [this message]
2009-05-21 20:15           ` Dominick Grift

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=1242908392.3001.8.camel@notebook2.grift.internal \
    --to=domg472@gmail.com \
    --cc=SELinux@tycho.nsa.gov \
    --cc=dwalsh@redhat.com \
    --cc=ewalsh@tycho.nsa.gov \
    --cc=sds@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.