diff options
| author | Jeff Layton | 2014-08-22 18:26:36 +0200 |
|---|---|---|
| committer | Jeff Layton | 2014-10-07 20:06:12 +0200 |
| commit | 415b96c5a1fe31ed9deb0618e95ecbb1df3de54c (patch) | |
| tree | be4fbf6503911abac9a71fc0856c3e7a9b27e221 /fs/locks.c | |
| parent | locks: close potential race in lease_get_mtime (diff) | |
| download | kernel-qcow2-linux-415b96c5a1fe31ed9deb0618e95ecbb1df3de54c.tar.gz kernel-qcow2-linux-415b96c5a1fe31ed9deb0618e95ecbb1df3de54c.tar.xz kernel-qcow2-linux-415b96c5a1fe31ed9deb0618e95ecbb1df3de54c.zip | |
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 <bfields@fieldses.org>
Signed-off-by: Jeff Layton <jlayton@primarydata.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Diffstat (limited to 'fs/locks.c')
0 files changed, 0 insertions, 0 deletions