From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 0/5][RESEND]NFSD/SUNRPC: Fix memory leak for the backchannel
Date: Mon, 31 Mar 2014 17:37:48 -0400 [thread overview]
Message-ID: <20140331213748.GE20024@fieldses.org> (raw)
In-Reply-To: <532FAC85.20909@gmail.com>
On Mon, Mar 24, 2014 at 11:54:45AM +0800, Kinglong Mee wrote:
> When using pynfs test-site, I found some memory leak for the backchannel.
All applied, thanks.--b.
>
> Kinglong Mee (5):
> NFSD: Using free_conn free connection
> NFSD: Free backchannel xprt in bc_destroy
> SUNRPC: New helper for creating client with rpc_xprt
> NFSD/SUNRPC: Check rpc_xprt out of xs_setup_bc_tcp
> SUNRPC: Clear xpt_bc_xprt if xs_setup_bc_tcp failed
>
> fs/nfsd/nfs4callback.c | 19 ++++++++++++++-
> fs/nfsd/nfs4state.c | 3 ++-
> include/linux/sunrpc/clnt.h | 2 ++
> include/linux/sunrpc/xprt.h | 13 +++++++++-
> net/sunrpc/clnt.c | 58 ++++++++++++++++++++++++++-------------------
> net/sunrpc/xprt.c | 12 ----------
> net/sunrpc/xprtsock.c | 15 +++++-------
> 7 files changed, 73 insertions(+), 49 deletions(-)
>
> --
> 1.8.5.3
prev parent reply other threads:[~2014-03-31 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-24 3:54 [PATCH 0/5][RESEND]NFSD/SUNRPC: Fix memory leak for the backchannel Kinglong Mee
2014-03-24 3:56 ` [PATCH 1/5][RESEND] NFSD: Using free_conn free connection Kinglong Mee
2014-03-24 3:58 ` [PATCH 2/5][RESEND] NFSD: Free backchannel xprt in bc_destroy Kinglong Mee
2014-03-24 3:58 ` [PATCH 3/5][RESEND] SUNRPC: New helper for creating client with rpc_xprt Kinglong Mee
2014-03-24 3:59 ` [PATCH 4/5][RESEND] NFSD/SUNRPC: Check rpc_xprt out of xs_setup_bc_tcp Kinglong Mee
2014-03-24 4:00 ` [PATCH 5/5][RESEND] SUNRPC: Clear xpt_bc_xprt if xs_setup_bc_tcp failed Kinglong Mee
2014-03-31 21:37 ` J. Bruce Fields [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140331213748.GE20024@fieldses.org \
--to=bfields@fieldses.org \
--cc=kinglongmee@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@primarydata.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).