summaryrefslogtreecommitdiffstats
path: root/sys/fs/nfs
diff options
context:
space:
mode:
authorrmacklem <rmacklem@FreeBSD.org>2011-06-22 21:10:12 +0000
committerrmacklem <rmacklem@FreeBSD.org>2011-06-22 21:10:12 +0000
commitda3820480591190db96ab7683ee5d3f085cdb7e2 (patch)
tree1de339d8a3477417580a1064fd97800577b3157c /sys/fs/nfs
parent83fca1d193659201a31cad508665386117ffdd5d (diff)
downloadFreeBSD-src-da3820480591190db96ab7683ee5d3f085cdb7e2.zip
FreeBSD-src-da3820480591190db96ab7683ee5d3f085cdb7e2.tar.gz
Plug an mbuf leak in the new NFS client that occurred when a
server replied NFS3ERR_JUKEBOX/NFS4ERR_DELAY to an rpc. This affected both NFSv3 and NFSv4. Found during testing at the recent NFSv4 interoperability Bakeathon. MFC after: 2 weeks
Diffstat (limited to 'sys/fs/nfs')
-rw-r--r--sys/fs/nfs/nfs_commonkrpc.c2
1 files changed, 2 insertions, 0 deletions
diff --git a/sys/fs/nfs/nfs_commonkrpc.c b/sys/fs/nfs/nfs_commonkrpc.c
index c34ea87..f658ac8 100644
--- a/sys/fs/nfs/nfs_commonkrpc.c
+++ b/sys/fs/nfs/nfs_commonkrpc.c
@@ -733,6 +733,8 @@ tryagain:
while (NFSD_MONOSEC < waituntil)
(void) nfs_catnap(PZERO, 0, "nfstry");
trylater_delay *= 2;
+ m_freem(nd->nd_mrep);
+ nd->nd_mrep = NULL;
goto tryagain;
}
OpenPOWER on IntegriCloud