[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080602104203.GA21898@infradead.org>
Date: Mon, 2 Jun 2008 06:42:03 -0400
From: Christoph Hellwig <hch@...radead.org>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: hch@...radead.org, linux-security-module@...r.kernel.org,
linux-fsdevel@...r.kernel.org, jmorris@...ei.org,
sds@...ho.nsa.gov, eparis@...hat.com, casey@...aufler-ca.com,
agruen@...e.de, jjohansen@...e.de,
penguin-kernel@...ove.SAKURA.ne.jp, viro@...IV.linux.org.uk,
linux-kernel@...r.kernel.org
Subject: Re: [patch 01/15] security: pass path to inode_create
On Mon, Jun 02, 2008 at 11:52:52AM +0200, Miklos Szeredi wrote:
> These patches fix several issues raised at previous submissions:
>
> - passing NULL vfsmounts
> - using nameidata
> - using extra stack for vfsmount argument
>
> So, it seems to me that there's in fact no issues remaining and the
> best excuse you can come up with is that it's a dumb idea. Well,
> that's not a very imressive technical argument IMNSHO.
Well, pathname based access control is a dumb idea, and we've been
through this N times. You've also been told that vfs_ routines should
remain without vfsmount, and no that's not a stack-related issue no idea
where that part came from.
--
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