From: Jeff Layton Date: Wed, 10 Oct 2012 20:43:21 +0000 (-0400) Subject: procfs: don't need a PATH_MAX allocation to hold a string representation of an int X-Git-Tag: firefly_0821_release~3680^2~1836^2 X-Git-Url: http://demsky.eecs.uci.edu/git/?a=commitdiff_plain;h=f81700bd831efcd12eb7f0e66b24b16c2ad00a32;p=firefly-linux-kernel-4.4.55.git procfs: don't need a PATH_MAX allocation to hold a string representation of an int Signed-off-by: Jeff Layton Signed-off-by: Al Viro --- diff --git a/fs/proc/base.c b/fs/proc/base.c index ef5c84be66f9..144a96732dd7 100644 --- a/fs/proc/base.c +++ b/fs/proc/base.c @@ -2258,7 +2258,8 @@ static void *proc_self_follow_link(struct dentry *dentry, struct nameidata *nd) pid_t tgid = task_tgid_nr_ns(current, ns); char *name = ERR_PTR(-ENOENT); if (tgid) { - name = __getname(); + /* 11 for max length of signed int in decimal + NULL term */ + name = kmalloc(12, GFP_KERNEL); if (!name) name = ERR_PTR(-ENOMEM); else @@ -2273,7 +2274,7 @@ static void proc_self_put_link(struct dentry *dentry, struct nameidata *nd, { char *s = nd_get_link(nd); if (!IS_ERR(s)) - __putname(s); + kfree(s); } static const struct inode_operations proc_self_inode_operations = {