p9: Fix leak of waitqueue in request allocation path
authorTom Tucker <tom@opengridcomputing.com>
Thu, 23 Oct 2008 21:33:25 +0000 (16:33 -0500)
committerEric Van Hensbergen <ericvh@gmail.com>
Wed, 5 Nov 2008 19:19:06 +0000 (13:19 -0600)
commit45abdf1c7be80d6ec3b0b14e59ee75a0d5d9fb37
tree34a5ea23b63df0da422ff161ec580f9b2ca54680
parent82b189eaaf6186b7694317632255fa87460820a0
p9: Fix leak of waitqueue in request allocation path

If a T or R fcall cannot be allocated, the function returns an error
but neglects to free the wait queue that was successfully allocated.

If it comes through again a second time this wq will be overwritten
with a new allocation and the old allocation will be leaked.

Also, if the client is subsequently closed, the close path will
attempt to clean up these allocations, so set the req fields to
NULL to avoid duplicate free.

Signed-off-by: Tom Tucker <tom@opengridcomputing.com>
Signed-off-by: Eric Van Hensbergen <ericvh@gmail.com>
net/9p/client.c