Re: [RFC] The reflink(2) system call v2.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 7 May 2009, Joel Becker wrote:


> @@ -1402,6 +1419,8 @@ struct security_operations {
>  			  struct dentry *new_dentry);
>  	int (*path_rename) (struct path *old_dir, struct dentry *old_dentry,
>  			    struct path *new_dir, struct dentry *new_dentry);
> +	int (*path_reflink) (struct dentry *old_dentry, struct path *new_dir,
> +			     struct dentry *new_dentry);
>  #endif
>  

The TOMOYO folk don't need a path hook, so it would be unused, and should 
not be added unless someone responsible for an in-tree LSM establishes a 
case for it.

> +int security_inode_reflink(struct dentry *old_dentry, struct inode *dir,
> +			   struct dentry *new_dentry);

We don't need the new_dentry argument (this is correct in the low-level 
hook, and doesn't compile with CONFIG_SECURITY=y).


- James
-- 
James Morris
<jmorris@xxxxxxxxx>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux