Re: [TOMOYO #6 retry 02/21] Add struct vfsmount to struct task_struct.

Serge: > Right, but one will be preferred by the community - and while I have my > own preference, I wouldn't put too much faith on that, rather talk with > the apparmor folks, look over the lkml logs for previous submissions, > and then decide. Thanks for your advice. We got the same advice from [

Re: [TOMOYO #6 retry 02/21] Add struct vfsmount to struct task_struct.

Quoting Kentaro Takeda ([EMAIL PROTECTED]): > Hello. > > Serge E. Hallyn wrote: > > I must say I personally prefer the apparmor approach. > No problem. > > > But I'd recommend > > you get together and get this piece pushed on its own, whichever version > > you can agree on. > TOMOYO can use AppAr

Re: [TOMOYO #6 retry 02/21] Add struct vfsmount to struct task_struct.

Hello. Serge E. Hallyn wrote: > I must say I personally prefer the apparmor approach. No problem. > But I'd recommend > you get together and get this piece pushed on its own, whichever version > you can agree on. TOMOYO can use AppArmor's patch. > Yes it needs a user, but at this point I would t

Re: [TOMOYO #6 retry 02/21] Add struct vfsmount to struct task_struct.

I must say I personally prefer the apparmor approach. But I'd recommend you get together and get this piece pushed on its own, whichever version you can agree on. Yes it needs a user, but at this point I would think both tomoyo and apparmor have had enough visibility that everyone knows the inten

[TOMOYO #6 retry 02/21] Add struct vfsmount to struct task_struct.

This patch allows VFS wrapper functions associate "struct vfsmount" with "struct task_struct" so that LSM hooks can calculate pathname of given "struct dentry". Signed-off-by: Tetsuo Handa <[EMAIL PROTECTED]> --- include/linux/init_task.h |1 + include/linux/sched.h |2 ++ 2 files cha