From: Jeff Layton Date: Fri, 22 Aug 2014 16:26:36 +0000 (-0400) Subject: nfsd: fix potential lease memory leak in nfs4_setlease X-Git-Tag: fixes-against-v3.18-rc2~119^2~13 X-Git-Url: http://git.openpandora.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=415b96c5a1fe31ed9deb0618e95ecbb1df3de54c;p=pandora-kernel.git nfsd: fix potential lease memory leak in nfs4_setlease It's unlikely to ever occur, but if there were already a lease set on the file then we could end up getting back a different pointer on a successful setlease attempt than the one we allocated. If that happens, the one we allocated could leak. In practice, I don't think this will happen due to the fact that we only try to set up the lease once per nfs4_file, but this error handling is a bit more correct given the current lease API. Cc: J. Bruce Fields Signed-off-by: Jeff Layton Reviewed-by: Christoph Hellwig --- Reading git-diff-tree failed