DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix cancelling health check alarm
Date: Mon, 19 Apr 2021 22:31:55 -0700	[thread overview]
Message-ID: <CACZ4nhtUHHmpmnypASbNKVYKt_aA8tNgtvXv0mGLfoYDGw_eQQ@mail.gmail.com> (raw)
In-Reply-To: <20210420040845.28725-1-kalesh-anakkur.purayil@broadcom.com>

[-- Attachment #1: Type: text/plain, Size: 1664 bytes --]

On Mon, Apr 19, 2021 at 8:46 PM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> Driver cancels the health check alarm only if error recovery is enabled
> in the FW. This can cause an issue. There is a small window where the
> driver receives the async event from fw and port close is invoked
> immediately. Driver clears BNXT_FLAG_RECOVERY_ENABLED flag when it gets
> the async event from FW. As a result, the health check alarm will not
> get canceled during port close and causes a segfault when the alarm tries
> to read Heartbeat register.
>
> Fix this by cancelling the health check alarm unconditionally during
> port stop.
>
> Fixes: 9d0cbaecc91a ("net/bnxt: support periodic FW health monitoring")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
> Reviewed-by: Ajit Kumar Khaparde <ajit.khaparde@broadcom.com>
Patch applied to dpdk-next-net-brcm.

> ---
>  drivers/net/bnxt/bnxt_ethdev.c | 3 ---
>  1 file changed, 3 deletions(-)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
> index 9da817f..f5d2dc8 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -4274,9 +4274,6 @@ void bnxt_schedule_fw_health_check(struct bnxt *bp)
>
>  static void bnxt_cancel_fw_health_check(struct bnxt *bp)
>  {
> -       if (!bnxt_is_recovery_enabled(bp))
> -               return;
> -
>         rte_eal_alarm_cancel(bnxt_check_fw_health, (void *)bp);
>         bp->flags &= ~BNXT_FLAG_FW_HEALTH_CHECK_SCHEDULED;
>  }
> --
> 2.10.1
>

      reply	other threads:[~2021-04-20  5:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-20  4:08 Kalesh A P
2021-04-20  5:31 ` Ajit Khaparde [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=CACZ4nhtUHHmpmnypASbNKVYKt_aA8tNgtvXv0mGLfoYDGw_eQQ@mail.gmail.com \
    --to=ajit.khaparde@broadcom.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=kalesh-anakkur.purayil@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).