From: Leon Romanovsky <leon@kernel.org>
To: yanjun.zhu@linux.dev
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com
Subject: Re: [PATCHv3 1/1] RDMA/rxe: Fix qp error handler
Date: Wed, 27 Jul 2022 12:16:42 +0300 [thread overview]
Message-ID: <YuECen5fE+T8M1hj@unreal> (raw)
In-Reply-To: <20220726045631.183632-1-yanjun.zhu@linux.dev>
On Tue, Jul 26, 2022 at 12:56:31AM -0400, yanjun.zhu@linux.dev wrote:
> From: Zhu Yanjun <yanjun.zhu@linux.dev>
>
> About 7 spin locks in qp creation needs to be initialized. Now these
> spin locks are initialized in the function rxe_qp_init_misc. This
> will avoid the error "initialize spin locks before use".
>
> Reported-by: syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com
> Signed-off-by: Zhu Yanjun <yanjun.zhu@linux.dev>
> ---
> V2->V3: Keep the spin_lock_init in rxe_init_task for future use.
> ---
> drivers/infiniband/sw/rxe/rxe_qp.c | 12 ++++++++----
> 1 file changed, 8 insertions(+), 4 deletions(-)
Fixes line?
>
> diff --git a/drivers/infiniband/sw/rxe/rxe_qp.c b/drivers/infiniband/sw/rxe/rxe_qp.c
> index 22e9b85344c3..ae8c51ef2db6 100644
> --- a/drivers/infiniband/sw/rxe/rxe_qp.c
> +++ b/drivers/infiniband/sw/rxe/rxe_qp.c
> @@ -174,6 +174,14 @@ static void rxe_qp_init_misc(struct rxe_dev *rxe, struct rxe_qp *qp,
>
> spin_lock_init(&qp->state_lock);
>
> + spin_lock_init(&qp->req.task.state_lock);
> + spin_lock_init(&qp->resp.task.state_lock);
> + spin_lock_init(&qp->comp.task.state_lock);
> +
> + spin_lock_init(&qp->sq.sq_lock);
> + spin_lock_init(&qp->rq.producer_lock);
> + spin_lock_init(&qp->rq.consumer_lock);
> +
> atomic_set(&qp->ssn, 0);
> atomic_set(&qp->skb_out, 0);
> }
> @@ -233,7 +241,6 @@ static int rxe_qp_init_req(struct rxe_dev *rxe, struct rxe_qp *qp,
> qp->req.opcode = -1;
> qp->comp.opcode = -1;
>
> - spin_lock_init(&qp->sq.sq_lock);
> skb_queue_head_init(&qp->req_pkts);
>
> rxe_init_task(rxe, &qp->req.task, qp,
> @@ -284,9 +291,6 @@ static int rxe_qp_init_resp(struct rxe_dev *rxe, struct rxe_qp *qp,
> }
> }
>
> - spin_lock_init(&qp->rq.producer_lock);
> - spin_lock_init(&qp->rq.consumer_lock);
> -
> skb_queue_head_init(&qp->resp_pkts);
>
> rxe_init_task(rxe, &qp->resp.task, qp,
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-07-27 9:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 4:56 [PATCHv3 1/1] RDMA/rxe: Fix qp error handler yanjun.zhu
2022-07-27 9:16 ` Leon Romanovsky [this message]
2022-07-27 12:38 ` Yanjun Zhu
2022-07-28 16:38 ` Jason Gunthorpe
2022-07-30 13:14 ` Yanjun Zhu
2022-07-30 14:01 ` Yanjun Zhu
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=YuECen5fE+T8M1hj@unreal \
--to=leon@kernel.org \
--cc=jgg@ziepe.ca \
--cc=linux-rdma@vger.kernel.org \
--cc=syzbot+833061116fa28df97f3b@syzkaller.appspotmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox