From: shaobingqing <shaobingqing@bwstor.com.cn>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linuxnfs <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH] SUNRPC: Fix potential memory scribble in xprt_free_bc_request()
Date: Wed, 12 Feb 2014 10:12:23 +0800 [thread overview]
Message-ID: <CALrKORqBECRi5jHNJNoXHQSy9rBYw+2=cD96ZVakEejCtzRB_w@mail.gmail.com> (raw)
In-Reply-To: <1392147810-23405-1-git-send-email-trond.myklebust@primarydata.com>
2014-02-12 3:43 GMT+08:00 Trond Myklebust <trond.myklebust@primarydata.com>:
> The call to xprt_free_allocation() will call list_del() on
> req->rq_bc_pa_list, which is not attached to a list.
Since the type of req->rq_bc_pa_list is struct list_head, I think it
is right on the tmp_list or
the xprt->bc_pa_list. Do I misunderstand sth?
> This patch moves the list_del() out of xprt_free_allocation()
> and into those callers that need it.
>
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
> net/sunrpc/backchannel_rqst.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/net/sunrpc/backchannel_rqst.c b/net/sunrpc/backchannel_rqst.c
> index 890a29912d5a..e860d4f7ed2a 100644
> --- a/net/sunrpc/backchannel_rqst.c
> +++ b/net/sunrpc/backchannel_rqst.c
> @@ -64,7 +64,6 @@ static void xprt_free_allocation(struct rpc_rqst *req)
> free_page((unsigned long)xbufp->head[0].iov_base);
> xbufp = &req->rq_snd_buf;
> free_page((unsigned long)xbufp->head[0].iov_base);
> - list_del(&req->rq_bc_pa_list);
> kfree(req);
> }
>
> @@ -168,8 +167,10 @@ out_free:
> /*
> * Memory allocation failed, free the temporary list
> */
> - list_for_each_entry_safe(req, tmp, &tmp_list, rq_bc_pa_list)
> + list_for_each_entry_safe(req, tmp, &tmp_list, rq_bc_pa_list) {
> + list_del(&req->rq_bc_pa_list);
> xprt_free_allocation(req);
> + }
>
> dprintk("RPC: setup backchannel transport failed\n");
> return -ENOMEM;
> @@ -198,6 +199,7 @@ void xprt_destroy_backchannel(struct rpc_xprt *xprt, unsigned int max_reqs)
> xprt_dec_alloc_count(xprt, max_reqs);
> list_for_each_entry_safe(req, tmp, &xprt->bc_pa_list, rq_bc_pa_list) {
> dprintk("RPC: req=%p\n", req);
> + list_del(&req->rq_bc_pa_list);
> xprt_free_allocation(req);
> if (--max_reqs == 0)
> break;
> --
> 1.8.5.3
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2014-02-12 2:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-11 19:43 [PATCH] SUNRPC: Fix potential memory scribble in xprt_free_bc_request() Trond Myklebust
2014-02-12 2:12 ` shaobingqing [this message]
2014-02-12 3:47 ` Trond Myklebust
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='CALrKORqBECRi5jHNJNoXHQSy9rBYw+2=cD96ZVakEejCtzRB_w@mail.gmail.com' \
--to=shaobingqing@bwstor.com.cn \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.