On Sun, 16 Feb 2014 20:31:01 +0800 Fabian Frederick <f...@skynet.be> wrote:

> Any user can display extented attribute names without read
> access.
> 
> eg: attr -l <filename>
> 
> This patch checks inode_permission in listxattr common
> function before executing vfs_listxattr.
> 
> ...
>
> --- a/fs/xattr.c
> +++ b/fs/xattr.c
> @@ -543,6 +543,10 @@ listxattr(struct dentry *d, char __user *list, size_t 
> size)
>       char *klist = NULL;
>       char *vlist = NULL;     /* If non-NULL, we used vmalloc() */
>  
> +     error = inode_permission(d->d_inode, MAY_READ);
> +     if (error)
> +             return error;
> +
>       if (size) {
>               if (size > XATTR_LIST_MAX)
>                       size = XATTR_LIST_MAX;

erk.  Doesn't this mean that if existing userspace is relying on the
current behaviour, this patch will cause breakage?

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to