diff options
author | Dan Carpenter <error27@gmail.com> | 2010-03-06 15:02:22 +0300 |
---|---|---|
committer | Trond Myklebust <Trond.Myklebust@netapp.com> | 2010-03-08 22:10:00 +0300 |
commit | 7dd08a570dcf45d52155996fee688405635ee481 (patch) | |
tree | 7458eddbaabf695fbaadbbc35d7deb71bfa45ab5 /fs | |
parent | 5fe46e9d733f19a880ef7e516002bd4c2b833e14 (diff) | |
download | linux-7dd08a570dcf45d52155996fee688405635ee481.tar.xz |
nfs: fix unlikely memory leak
I'll admit that it's unlikely for the first allocation to fail and
the second one to succeed. I won't be offended if you ignore this
patch.
Signed-off-by: Dan Carpenter <error27@gmail.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
Diffstat (limited to 'fs')
-rw-r--r-- | fs/nfs/nfs4proc.c | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c index eda74c42d552..f9254fb0c9d0 100644 --- a/fs/nfs/nfs4proc.c +++ b/fs/nfs/nfs4proc.c @@ -5107,6 +5107,7 @@ static int nfs41_proc_async_sequence(struct nfs_client *clp, res = kzalloc(sizeof(*res), GFP_KERNEL); if (!args || !res) { kfree(args); + kfree(res); nfs_put_client(clp); return -ENOMEM; } |