[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140109222809.GL10323@ZenIV.linux.org.uk>
Date: Thu, 9 Jan 2014 22:28:10 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Eric Paris <eparis@...hat.com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
LKML <linux-kernel@...r.kernel.org>,
Stephen Smalley <sds@...ho.nsa.gov>,
James Morris <james.l.morris@...cle.com>,
Paul Moore <paul@...l-moore.com>,
Andrew Morton <akpm@...ux-foundation.org>,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
stable <stable@...r.kernel.org>, selinux@...ho.nsa.gov,
linux-security-module@...r.kernel.org
Subject: Re: [PATCH] SELinux: Fix possible NULL pointer dereference in
selinux_inode_permission()
On Thu, Jan 09, 2014 at 11:05:45AM -0500, Eric Paris wrote:
> [adding lsm and selinux]
>
> Am I just crazy, or was this bug discussed (and obviously not fixed)
> some time ago?
>
> VFS can still use inodes after security_inode_free_security() was
> called...
Unrelated bug.
> > Assuming the VFS guys say that delaying __destroy_inode() is safe like
> > that, I like it better. It also means that this is fixed for all LSMs,
> > not just SELinux...
Recall what your own code called from __destroy_inode() (fsnotify horrors)
is doing - you can't grab a mutex from RCU callback...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists