[PATCH -v3] SELinux: Add get, set, and cloning of superblock security information

2007-11-09 Thread Eric Paris
on to understand security should be in the FS which owns the options. Signed-off-by: Eric Paris <[EMAIL PROTECTED]> --- For now the only forseen user of this interface is NFS. NFS uses a binary blob in kernel for mount data (it uses this blob irrespective of the binary vs. text mount opt

Re: [PATCH -v3] SELinux: Add get, set, and cloning of superblock security information

2007-11-09 Thread Eric Paris
On Fri, 2007-11-09 at 14:46 -0800, Casey Schaufler wrote: > --- Eric Paris <[EMAIL PROTECTED]> wrote: > > > Adds security_get_sb_mnt_opts, security_set_sb_mnt_opts, and > > security_clont_sb_mnt_opts to the LSM and to SELinux. This will allow > > filesystems to d

Re: [PATCH -v3] SELinux: Add get, set, and cloning of superblock security information

2007-11-28 Thread Eric Paris
asic meaning I guess) > and any FS which decides to own there own security options would need to > be patched to use this new interface for every possible LSM. This is > because it was stated to me very clearly that LSM's should not attempt > to understand FS mount data and the burdon t

Re: NFS/LSM: allow NFS to control all of its own mount options

2008-02-19 Thread Eric Paris
On Tue, 2008-02-19 at 17:24 -0500, Christoph Hellwig wrote: > Please don't introduce a special case for just nfs. All filesystems > should control their mount options, so please provide some library > helpers for context= handling and move it into all filesystems that > can support selinux. A li

Re: NFS/LSM: allow NFS to control all of its own mount options

2008-02-20 Thread Eric Paris
On Wed, 2008-02-20 at 08:50 -0500, Stephen Smalley wrote: > On Wed, 2008-02-20 at 11:08 +0100, Miklos Szeredi wrote: > > > Please don't introduce a special case for just nfs. All filesystems > > > should control their mount options, so please provide some library > > > helpers for context= handli