From: Rui Xiang <rui.xi...@huawei.com>

While kzallocing sbi/ino fails, it should return -ENOMEM.

And it should return the err value from autofs_prepare_pipe.

Signed-off-by: Rui Xiang <rui.xi...@huawei.com>
Acked-by: Ian Kent <ra...@themaw.net>
---
 fs/autofs4/inode.c |   13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/fs/autofs4/inode.c b/fs/autofs4/inode.c
index 3b9cc9b..07d22c0 100644
--- a/fs/autofs4/inode.c
+++ b/fs/autofs4/inode.c
@@ -206,10 +206,11 @@ int autofs4_fill_super(struct super_block *s, void *data, 
int silent)
        int pipefd;
        struct autofs_sb_info *sbi;
        struct autofs_info *ino;
+       int ret = -EINVAL;
 
        sbi = kzalloc(sizeof(*sbi), GFP_KERNEL);
        if (!sbi)
-               goto fail_unlock;
+               return -ENOMEM;
        DPRINTK("starting up, sbi = %p",sbi);
 
        s->s_fs_info = sbi;
@@ -243,8 +244,10 @@ int autofs4_fill_super(struct super_block *s, void *data, 
int silent)
         * Get the root inode and dentry, but defer checking for errors.
         */
        ino = autofs4_new_ino(sbi);
-       if (!ino)
+       if (!ino) {
+               ret = -ENOMEM;
                goto fail_free;
+       }
        root_inode = autofs4_get_inode(s, S_IFDIR | 0755);
        root = d_make_root(root_inode);
        if (!root)
@@ -291,7 +294,8 @@ int autofs4_fill_super(struct super_block *s, void *data, 
int silent)
                printk("autofs: could not open pipe file descriptor\n");
                goto fail_dput;
        }
-       if (autofs_prepare_pipe(pipe) < 0)
+       ret = autofs_prepare_pipe(pipe);
+       if (ret < 0)
                goto fail_fput;
        sbi->pipe = pipe;
        sbi->pipefd = pipefd;
@@ -318,8 +322,7 @@ fail_ino:
 fail_free:
        kfree(sbi);
        s->s_fs_info = NULL;
-fail_unlock:
-       return -EINVAL;
+       return ret;
 }
 
 struct inode *autofs4_get_inode(struct super_block *sb, umode_t mode)

--
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