[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1K2uXZ-0001eE-Oi@pomaz-ex.szeredi.hu>
Date: Sun, 01 Jun 2008 22:52:33 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: hch@...radead.org
CC: miklos@...redi.hu, 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, hch@...radead.org,
viro@...IV.linux.org.uk, linux-kernel@...r.kernel.org
Subject: Re: [patch 01/15] security: pass path to inode_create
> >
> > In the inode_create() security operation and related functions pass
> > the path (vfsmount + dentry) to the parent directory instead of the
> > inode. AppArmor will need this.
>
> So you're once again switching vfs_ to a pass a vfsmount argument, this
> time hidden under struct path. It's really hard to grasp a "no"
> sometimes, isn't it? :)
I'm sorry Christoph, but have you considered the remote possibility,
that you and Al are both wrong on this one? Well, there's one
excercise for you.
If you haven't noticed, I don't take "no" for an answer, until I'm
sufficiently convinced that there's a better way. In this case I
haven't heard a solution, that is remotely close in cleanliness to
what I've proposed. And also please note that "not merging apparmor"
is _not_ the answer, however much you would like that to be. So
please try harder to find an alternative, and then I'll listen.
Miklos
--
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