From: Bob Pearson <rpearsonhpe@gmail.com>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Zhu Yanjun <zyjzyj2000@gmail.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>
Cc: linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
linux-rdma@vger.kernel.org
Subject: Re: [PATCH] RDMA/rxe: Fix an error handling path in rxe_bind_mw()
Date: Mon, 17 Jul 2023 17:31:09 -0500 [thread overview]
Message-ID: <b5880a47-aaa4-cb5e-e1f6-00f17695efe8@gmail.com> (raw)
In-Reply-To: <43698d8a3ed4e720899eadac887427f73d7ec2eb.1689623735.git.christophe.jaillet@wanadoo.fr>
On 7/17/23 14:55, Christophe JAILLET wrote:
> All errors go to the error handling path, except this one. Be consistent
> and also branch to it.
>
> Fixes: 02ed253770fb ("RDMA/rxe: Introduce rxe access supported flags")
> Signed-off-by: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
> ---
> /!\ Speculative /!\
>
> This patch is based on analysis of the surrounding code and should be
> reviewed with care !
>
> /!\ Speculative /!\
> ---
> drivers/infiniband/sw/rxe/rxe_mw.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_mw.c b/drivers/infiniband/sw/rxe/rxe_mw.c
> index d8a43d87de93..d9312b5c9d20 100644
> --- a/drivers/infiniband/sw/rxe/rxe_mw.c
> +++ b/drivers/infiniband/sw/rxe/rxe_mw.c
> @@ -199,7 +199,8 @@ int rxe_bind_mw(struct rxe_qp *qp, struct rxe_send_wqe *wqe)
>
> if (access & ~RXE_ACCESS_SUPPORTED_MW) {
> rxe_err_mw(mw, "access %#x not supported", access);
> - return -EOPNOTSUPP;
> + ret = -EOPNOTSUPP;
> + goto err_drop_mr;
> }
>
> spin_lock_bh(&mw->lock);
Christophe,
Good catch. Thanks. Probably should go to for-next.
Bob
Reviewed-by: Bob Pearson <rpearsonhpe@gmail.com>
next prev parent reply other threads:[~2023-07-17 22:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-17 19:55 [PATCH] RDMA/rxe: Fix an error handling path in rxe_bind_mw() Christophe JAILLET
2023-07-17 22:31 ` Bob Pearson [this message]
2023-07-17 23:20 ` Zhu Yanjun
-- strict thread matches above, loose matches on Subject: below --
2023-07-18 12:30 Leon Romanovsky
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=b5880a47-aaa4-cb5e-e1f6-00f17695efe8@gmail.com \
--to=rpearsonhpe@gmail.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=jgg@ziepe.ca \
--cc=kernel-janitors@vger.kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=zyjzyj2000@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