From: Allison Henderson <achender@kernel.org>
To: Ren Wei <n05ec@lzu.edu.cn>,
netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
rds-devel@oss.oracle.com
Cc: davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, horms@kernel.org, leon@kernel.org,
santosh.shilimkar@oracle.com, jhubbard@nvidia.com,
yuantan098@gmail.com, yifanwucs@gmail.com,
tomapufckgml@gmail.com, bird@lzu.edu.cn, draw51280@163.com
Subject: Re: [PATCH net 1/1] net: rds: fix MR cleanup on copy error
Date: Wed, 22 Apr 2026 22:39:08 -0700 [thread overview]
Message-ID: <15512dc3c3250ae025f9e588e2335e2a2acf5107.camel@kernel.org> (raw)
In-Reply-To: <79c8ef73ec8e5844d71038983940cc2943099baf.1776764247.git.draw51280@163.com>
On Wed, 2026-04-22 at 22:52 +0800, Ren Wei wrote:
> From: Ao Zhou <draw51280@163.com>
>
> __rds_rdma_map() hands sg/pages ownership to the transport after
> get_mr() succeeds. If copying the generated cookie back to user space
> fails after that point, the error path must not free those resources
> again before dropping the MR reference.
>
> Remove the duplicate unpin/free from the put_user() failure branch so
> that MR teardown is handled only through the existing final cleanup
> path.
>
> Fixes: 0d4597c8c5ab ("net/rds: Track user mapped pages through special API")
> Cc: stable@kernel.org
> Reported-by: Yuan Tan <yuantan098@gmail.com>
> Reported-by: Yifan Wu <yifanwucs@gmail.com>
> Reported-by: Juefei Pu <tomapufckgml@gmail.com>
> Reported-by: Xin Liu <bird@lzu.edu.cn>
> Signed-off-by: Ao Zhou <draw51280@163.com>
> Signed-off-by: Ren Wei <n05ec@lzu.edu.cn>
Hi Aso,
This fix looks good to me. Since this is a bug fix, this patch should be cc'd to stable@vger.kernel.org. Also be sure
to note the target tree and component in the subject line like this:
[PATCH net v2 1/1] net/net: rds: fix MR cleanup on copy error
Other than that, the patch looks good to me. Thanks Aso.
Reviewed-by: Allison Henderson <achender@kernel.org>
Allison
> ---
> net/rds/rdma.c | 4 ----
> 1 file changed, 4 deletions(-)
>
> diff --git a/net/rds/rdma.c b/net/rds/rdma.c
> index aa6465dc742c..61fb6e45281b 100644
> --- a/net/rds/rdma.c
> +++ b/net/rds/rdma.c
> @@ -326,10 +326,6 @@ static int __rds_rdma_map(struct rds_sock *rs, struct rds_get_mr_args *args,
>
> if (args->cookie_addr &&
> put_user(cookie, (u64 __user *)(unsigned long)args->cookie_addr)) {
> - if (!need_odp) {
> - unpin_user_pages(pages, nr_pages);
> - kfree(sg);
> - }
> ret = -EFAULT;
> goto out;
> }
prev parent reply other threads:[~2026-04-23 5:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <cover.1776764247.git.draw51280@163.com>
2026-04-22 14:52 ` [PATCH net 1/1] net: rds: fix MR cleanup on copy error Ren Wei
2026-04-23 5:39 ` Allison Henderson [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=15512dc3c3250ae025f9e588e2335e2a2acf5107.camel@kernel.org \
--to=achender@kernel.org \
--cc=bird@lzu.edu.cn \
--cc=davem@davemloft.net \
--cc=draw51280@163.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jhubbard@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=n05ec@lzu.edu.cn \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=santosh.shilimkar@oracle.com \
--cc=tomapufckgml@gmail.com \
--cc=yifanwucs@gmail.com \
--cc=yuantan098@gmail.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