All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: James Morris <jmorris@namei.org>
Cc: selinux <selinux@tycho.nsa.gov>, Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH] SELinux: requesting no permissions in avc_has_perm_noaudit is a BUG()
Date: Wed, 12 Mar 2008 12:44:28 -0400	[thread overview]
Message-ID: <1205340268.5297.194.camel@localhost.localdomain> (raw)
In-Reply-To: <Xine.LNX.4.64.0803120924590.26039@us.intercode.com.au>

On Wed, 2008-03-12 at 09:26 +1100, James Morris wrote:
> On Wed, 12 Mar 2008, James Morris wrote:
> 
> > Applied to 
> > git://git.kernel.org/pub/scm/linux/kernel/git/jmorris/selinux-2.6.git#for-akpm
> 
> Just saw this during boot.
> 
> [    8.238863] ------------[ cut here ]------------
> [    8.239762] kernel BUG at security/selinux/avc.c:874!

turns out this is easy to reproduce.

#include <sys/types.h>
#include <sys/stat.h>
#include <fcntl.h>

int main(void)
{
	open("/dev/null", 3);
	return 0;
}

I'm testing a new patch which once I full understand I'll send upstream
to see what they have to say...

-Eric


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

      parent reply	other threads:[~2008-03-12 16:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-11 18:19 [PATCH] SELinux: requesting no permissions in avc_has_perm_noaudit is a BUG() Eric Paris
2008-03-11 18:35 ` Stephen Smalley
2008-03-11 22:16 ` James Morris
2008-03-11 22:26   ` James Morris
2008-03-12  1:10     ` Eric Paris
2008-03-12 13:05       ` Stephen Smalley
2008-03-12 15:31     ` Eric Paris
2008-03-12 17:18       ` Stephen Smalley
2008-03-12 17:40         ` Eric Paris
2008-03-12 16:44     ` Eric Paris [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=1205340268.5297.194.camel@localhost.localdomain \
    --to=eparis@redhat.com \
    --cc=jmorris@namei.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.