From: Leon Romanovsky <leon@kernel.org>
To: Weihang Li <liweihang@huawei.com>
Cc: dledford@redhat.com, jgg@nvidia.com, linux-rdma@vger.kernel.org,
linuxarm@huawei.com
Subject: Re: [PATCH for-next] RDMA/core: Check invalid QP state for ib_modify_qp_is_ok()
Date: Sat, 20 Mar 2021 11:34:30 +0200 [thread overview]
Message-ID: <YFXBprYFmFgHu9Z8@unreal> (raw)
In-Reply-To: <1616144545-18159-1-git-send-email-liweihang@huawei.com>
On Fri, Mar 19, 2021 at 05:02:25PM +0800, Weihang Li wrote:
> From: Xi Wang <wangxi11@huawei.com>
>
> Out-of-bounds may occur in 'qp_state_table' when the caller passing wrong
> QP state value.
How is it possible? Do you have call stack to support it?
Thanks
>
> Signed-off-by: Xi Wang <wangxi11@huawei.com>
> Signed-off-by: Weihang Li <liweihang@huawei.com>
> ---
> drivers/infiniband/core/verbs.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/drivers/infiniband/core/verbs.c b/drivers/infiniband/core/verbs.c
> index 28464c5..66ba4e6 100644
> --- a/drivers/infiniband/core/verbs.c
> +++ b/drivers/infiniband/core/verbs.c
> @@ -1613,6 +1613,10 @@ bool ib_modify_qp_is_ok(enum ib_qp_state cur_state, enum ib_qp_state next_state,
> cur_state != IB_QPS_SQD && cur_state != IB_QPS_SQE)
> return false;
>
> + if (cur_state >= ARRAY_SIZE(qp_state_table) ||
> + next_state >= ARRAY_SIZE(qp_state_table[0]))
> + return false;
> +
> if (!qp_state_table[cur_state][next_state].valid)
> return false;
>
> --
> 2.8.1
>
next prev parent reply other threads:[~2021-03-20 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-19 9:02 [PATCH for-next] RDMA/core: Check invalid QP state for ib_modify_qp_is_ok() Weihang Li
2021-03-20 9:34 ` Leon Romanovsky [this message]
2021-03-22 3:29 ` liweihang
2021-03-22 5:47 ` Leon Romanovsky
2021-03-22 6:21 ` liweihang
2021-03-22 7:11 ` liweihang
2021-03-22 7:28 ` Leon Romanovsky
2021-03-22 7:55 ` liweihang
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=YFXBprYFmFgHu9Z8@unreal \
--to=leon@kernel.org \
--cc=dledford@redhat.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=liweihang@huawei.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