Hi Trond,
On Fri, Apr 5, 2013 at 11:16 PM, Trond Myklebust
<Trond.Myklebust@xxxxxxxxxx> wrote:
> The following two sets of issues for the stable kernel were found when
> debugging the rpcsec_gss patches.
> Thanks to Bryan for helping with testing.
>
> Trond Myklebust (2):
> NFSv4: Fix a memory leak in nfs4_discover_server_trunking
> NFSv4/4.1: Fix bugs in nfs4[01]_walk_client_list
>
> fs/nfs/nfs4client.c | 44 ++++++++++++++++++++++++++++----------------
> fs/nfs/nfs4state.c | 8 +++++++-
> 2 files changed, 35 insertions(+), 17 deletions(-)
I was wondering why this commit is not tagged to go in stable as well:
commit f05c124a70a4953a66acbd6d6c601ea1eb5d0fa7
Author: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
Date: Fri Apr 5 14:13:21 2013 -0400
SUNRPC: Fix a potential memory leak in rpc_new_client
If the call to rpciod_up() fails, we currently leak a reference to the
struct rpc_xprt.
As part of the fix, we also remove the redundant check for xprt!=NULL.
This is already taken care of by the callers.
Signed-off-by: Trond Myklebust <Trond.Myklebust@xxxxxxxxxx>
http://git.linux-nfs.org/?p=trondmy/linux-nfs.git;a=commit;h=f05c124a70a4953a66acbd6d6c601ea1eb5d0fa7
Regards,
--
William
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
