The patch titled xattr: use memdup_user() has been added to the -mm tree. Its filename is xattr-use-memdup_user.patch Before you just go and hit "reply", please: a) Consider who else should be cc'ed b) Prefer to cc a suitable mailing list as well c) Ideally: find the original patch on the mailing list and do a reply-to-all to that, adding suitable additional cc's *** Remember to use Documentation/SubmitChecklist when testing your code *** See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find out what to do about this The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/ ------------------------------------------------------ Subject: xattr: use memdup_user() From: Li Zefan <lizf@xxxxxxxxxxxxxx> Remove open-coded memdup_user(). Signed-off-by: Li Zefan <lizf@xxxxxxxxxxxxxx> Cc: Andreas Gruenbacher <agruen@xxxxxxx> Cc: Al Viro <viro@xxxxxxxxxxxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> --- fs/xattr.c | 10 +++------- 1 file changed, 3 insertions(+), 7 deletions(-) diff -puN fs/xattr.c~xattr-use-memdup_user fs/xattr.c --- a/fs/xattr.c~xattr-use-memdup_user +++ a/fs/xattr.c @@ -237,13 +237,9 @@ setxattr(struct dentry *d, const char __ if (size) { if (size > XATTR_SIZE_MAX) return -E2BIG; - kvalue = kmalloc(size, GFP_KERNEL); - if (!kvalue) - return -ENOMEM; - if (copy_from_user(kvalue, value, size)) { - kfree(kvalue); - return -EFAULT; - } + kvalue = memdup_user(value, size); + if (IS_ERR(kvalue)) + return PTR_ERR(kvalue); } error = vfs_setxattr(d, kname, kvalue, size, flags); _ Patches currently in -mm which might be from lizf@xxxxxxxxxxxxxx are documentation-sysctl-nettxt-fix-a-typo.patch cls_cgroup-remove-unneeded-cgroup_lock.patch devcgroup-skip-superfluous-checks-when-found-the-dev_all-elem.patch xattr-use-memdup_user.patch btrfs-use-memdup_user.patch sysfs-use-memdup_user.patch xfs-use-memdup_user.patch ncpfs-use-memdup_user.patch ecryptfs-use-memdup_user.patch -- To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html