From: Leon Romanovsky <leon@kernel.org>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: jgg@ziepe.ca, linux-rdma@vger.kernel.org,
andrew.gospodarek@broadcom.com, kashyap.desai@broadcom.com
Subject: Re: [PATCH v2 for-next 10/17] RDMA/bnxt_re: handle command completions after driver detect a timedout
Date: Mon, 12 Jun 2023 10:07:26 +0300 [thread overview]
Message-ID: <20230612070726.GP12152@unreal> (raw)
In-Reply-To: <1686308514-11996-11-git-send-email-selvin.xavier@broadcom.com>
On Fri, Jun 09, 2023 at 04:01:47AM -0700, Selvin Xavier wrote:
> From: Kashyap Desai <kashyap.desai@broadcom.com>
>
> If calling context detect command timeout, associated memory stored on
> stack will not be valid. If firmware complete the same command later,
> this causes incorrect memory access by driver.
>
> Added is_waiter_alive to handle delayed completion by firmware.
> is_waiter_alive is set and reset under command queue lock.
>
> Signed-off-by: Kashyap Desai <kashyap.desai@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.c | 59 +++++++++++++++++-------------
> drivers/infiniband/hw/bnxt_re/qplib_rcfw.h | 1 +
> 2 files changed, 34 insertions(+), 26 deletions(-)
<...>
> /* Non zero means command completed */
This comment is not valid anymore.
> - ret = wait_event_timeout(cmdq->waitq,
> - !test_bit(cbit, cmdq->cmdq_bitmap),
> - msecs_to_jiffies(10000));
> + wait_event_timeout(cmdq->waitq,
> + !test_bit(cbit, cmdq->cmdq_bitmap),
> + msecs_to_jiffies(10000));
Thanks
next prev parent reply other threads:[~2023-06-12 7:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:01 [PATCH v2 for-next 00/17] RDMA/bnxt_re: Control path updates Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 01/17] RDMA/bnxt_re: wraparound mbox producer index Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 02/17] RDMA/bnxt_re: Avoid calling wake_up threads from spin_lock context Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 03/17] RDMA/bnxt_re: remove virt_func check while creating RoCE FW channel Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 04/17] RDMA/bnxt_re: set fixed command queue depth Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 05/17] RDMA/bnxt_re: Enhance the existing functions that wait for FW responses Selvin Xavier
2023-06-12 7:00 ` Leon Romanovsky
2023-06-09 11:01 ` [PATCH v2 for-next 06/17] RDMA/bnxt_re: Avoid the command wait if firmware is inactive Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 07/17] RDMA/bnxt_re: use shadow qd while posting non blocking rcfw command Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 08/17] RDMA/bnxt_re: Simplify the function that sends the FW commands Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 09/17] RDMA/bnxt_re: add helper function __poll_for_resp Selvin Xavier
2023-06-12 7:04 ` Leon Romanovsky
2023-06-12 8:01 ` Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 10/17] RDMA/bnxt_re: handle command completions after driver detect a timedout Selvin Xavier
2023-06-12 7:07 ` Leon Romanovsky [this message]
2023-06-09 11:01 ` [PATCH v2 for-next 11/17] RDMA/bnxt_re: Add firmware stall check detection Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 12/17] RDMA/bnxt_re: post destroy_ah for delayed completion of AH creation Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 13/17] RDMA/bnxt_re: consider timeout of destroy ah as success Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 14/17] RDMA/bnxt_re: cancel all control path command waiters upon error Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 15/17] RDMA/bnxt_re: use firmware provided max request timeout Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 16/17] RDMA/bnxt_re: remove redundant cmdq_bitmap Selvin Xavier
2023-06-09 11:01 ` [PATCH v2 for-next 17/17] RDMA/bnxt_re: optimize the parameters passed to helper functions Selvin Xavier
2023-06-12 7:12 ` [PATCH v2 for-next 00/17] RDMA/bnxt_re: Control path updates Leon Romanovsky
2023-06-12 7:12 ` 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=20230612070726.GP12152@unreal \
--to=leon@kernel.org \
--cc=andrew.gospodarek@broadcom.com \
--cc=jgg@ziepe.ca \
--cc=kashyap.desai@broadcom.com \
--cc=linux-rdma@vger.kernel.org \
--cc=selvin.xavier@broadcom.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;
as well as URLs for NNTP newsgroup(s).