All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: James Morris <jmorris@namei.org>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	Alexander Beregalov <a.beregalov@gmail.com>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Kernel Testers List <kernel-testers@vger.kernel.org>,
	Stephen Smalley <sds@tycho.nsa.gov>,
	Eric Paris <eparis@parisplace.org>
Subject: Re: BUG at security/selinux/avc.c:883 (was: Re: linux-next: Tree for July 17: early crash on x86-64)
Date: Sun, 20 Jul 2008 13:15:59 +0100	[thread overview]
Message-ID: <20080720121559.GV28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1216546973.3217.6.camel@dhcppc2>

On Sun, Jul 20, 2008 at 11:42:53AM +0200, Thomas Meyer wrote:
> Am Sonntag, den 20.07.2008, 05:54 +1000 schrieb James Morris:
> > On Sat, 19 Jul 2008, Rafael J. Wysocki wrote:
> > 
> > > > vfs-next/net-next conflict; apply the patch below on top of the
> > merge.
> > > 
> > > That helped, thanks.
> > > 
> > > But next it ran into the BUG_ON() in line 883 of
> > security/selinux/avc.c .
> > > Disabling selinux made the kernel boot, finally.
> > 
> > Ugh, that's not supposed to happen.  Where was this in the boot?  Do
> > you 
> > have a console log?

Argh...  Fallout from ->permission() patch series.  I've folded that into
rebase (along with Randy's compile fixes and missing bit in capability.c
in ->inode_permission() patch; AFAICS takes care of all mismerges as well).
In the meanwhile, see the patch below on top of next-20080718:

diff --git a/fs/namei.c b/fs/namei.c
index a15c155..c0a64e2 100644
--- a/fs/namei.c
+++ b/fs/namei.c
@@ -286,7 +286,8 @@ int permission(struct inode *inode, int mask, struct nameidata *nd)
 	if (retval)
 		return retval;
 
-	return security_inode_permission(inode, mask);
+	return security_inode_permission(inode,
+					mask & (MAY_READ|MAY_WRITE|MAY_EXEC));
 }
 
 /**

  reply	other threads:[~2008-07-20 12:15 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17 15:28 linux-next: Tree for July 17 Stephen Rothwell
2008-07-17 22:21 ` linux-next: Tree for July 17 (sysctl/syscall) Randy Dunlap
2008-07-17 22:34 ` linux-next: Tree for July 17 (net_namespace) Randy Dunlap
2008-07-17 23:06 ` linux-next: Tree for July 17: early crash on x86-64 Rafael J. Wysocki
2008-07-18 13:52   ` Alexander Beregalov
2008-07-19  3:52     ` Al Viro
     [not found]       ` <20080719035231.GU28946-3bDd1+5oDREiFSDQTTA3OLVCufUGDwFn@public.gmane.org>
2008-07-19 18:42         ` Rafael J. Wysocki
2008-07-19 18:42           ` Rafael J. Wysocki
2008-07-19 19:54           ` James Morris
     [not found]             ` <Xine.LNX.4.64.0807200553380.22632-RC8Ws/H8zzudju81dFSl6rpzq4S04n8Q@public.gmane.org>
2008-07-20  9:42               ` BUG at security/selinux/avc.c:883 (was: Re: linux-next: Tree for July 17: early crash on x86-64) Thomas Meyer
2008-07-20  9:42                 ` Thomas Meyer
2008-07-20 12:15                 ` Al Viro [this message]
2008-07-28 17:32                   ` Stephen Smalley
     [not found]                     ` <1217266358.20373.54.camel-/ugcdrsPCSfIm9DtXLC9OUVfdvkotuLY+aIohriVLy8@public.gmane.org>
2008-07-28 21:38                       ` James Morris
2008-07-28 21:38                         ` James Morris
     [not found]                         ` <Xine.LNX.4.64.0807290736440.30242-RC8Ws/H8zzudju81dFSl6rpzq4S04n8Q@public.gmane.org>
2008-07-29  0:33                           ` Al Viro
2008-07-29  0:33                             ` Al Viro

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=20080720121559.GV28946@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=a.beregalov@gmail.com \
    --cc=eparis@parisplace.org \
    --cc=jmorris@namei.org \
    --cc=kernel-testers@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rjw@sisk.pl \
    --cc=sds@tycho.nsa.gov \
    --cc=sfr@canb.auug.org.au \
    --cc=thomas@m3y3r.de \
    /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.