From: Leon Romanovsky <leon@kernel.org>
To: yanjun.zhu@linux.dev
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org
Subject: Re: [PATCHv2 1/1] RDMA/rxe: Fix BUG: KASAN: null-ptr-deref in rxe_qp_do_cleanup
Date: Mon, 18 Jul 2022 14:33:13 +0300 [thread overview]
Message-ID: <YtVE+YpjEwNrzmsQ@unreal> (raw)
In-Reply-To: <20220705225414.315478-1-yanjun.zhu@linux.dev>
On Tue, Jul 05, 2022 at 06:54:14PM -0400, yanjun.zhu@linux.dev wrote:
> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> The function rxe_create_qp calls rxe_qp_from_init. If some error
> occurs, the error handler of function rxe_qp_from_init will set
> both scq and rcq to NULL.
>
> Then rxe_create_qp calls rxe_put to handle qp. In the end,
> rxe_qp_do_cleanup is called by rxe_put. rxe_qp_do_cleanup directly
> accesses scq and rcq before checking them. This will cause
> null-ptr-deref error.
>
> The call graph is as below:
>
> rxe_create_qp {
> ...
> rxe_qp_from_init {
> ...
> err1:
> ...
> qp->rcq = NULL; <---rcq is set to NULL
> qp->scq = NULL; <---scq is set to NULL
> ...
> }
>
> qp_init:
> rxe_put{
> ...
> rxe_qp_do_cleanup {
> ...
> atomic_dec(&qp->scq->num_wq); <--- scq is accessed
> ...
> atomic_dec(&qp->rcq->num_wq); <--- rcq is accessed
> }
> }
>
> Fixes: 4703b4f0d94a ("RDMA/rxe: Enforce IBA C11-17")
> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
> ---
> V1->V2: Describe the error flows.
> ---
> drivers/infiniband/sw/rxe/rxe_qp.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
Thanks, applied.
prev parent reply other threads:[~2022-07-18 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 22:54 [PATCHv2 1/1] RDMA/rxe: Fix BUG: KASAN: null-ptr-deref in rxe_qp_do_cleanup yanjun.zhu
2022-07-05 10:35 ` Haris Iqbal
2022-07-06 13:10 ` Yanjun Zhu
2022-07-06 13:11 ` Haris Iqbal
2022-07-14 16:57 ` Bob Pearson
2022-07-18 11:33 ` Leon Romanovsky [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=YtVE+YpjEwNrzmsQ@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=yanjun.zhu@linux.dev \
/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.