Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
Vasundhara Volam <vasundhara-v.volam@broadcom.com>
Subject: Re: [PATCH net 2/2] bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task()
Date: Sun, 6 Sep 2020 12:25:34 -0700 [thread overview]
Message-ID: <20200906122534.54e16e08@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com> (raw)
In-Reply-To: <1599360937-26197-3-git-send-email-michael.chan@broadcom.com>
On Sat, 5 Sep 2020 22:55:37 -0400 Michael Chan wrote:
> From: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
>
> bnxt_fw_reset_task() which runs from a workqueue can race with
> bnxt_remove_one(). For example, if firmware reset and VF FLR are
> happening at about the same time.
>
> bnxt_remove_one() already cancels the workqueue and waits for it
> to finish, but we need to do this earlier before the devlink
> reporters are destroyed. This will guarantee that
> the devlink reporters will always be valid when bnxt_fw_reset_task()
> is still running.
>
> Fixes: b148bb238c02 ("bnxt_en: Fix possible crash in bnxt_fw_reset_task().")
> Reviewed-by: Edwin Peer <edwin.peer@broadcom.com>
> Signed-off-by: Vasundhara Volam <vasundhara-v.volam@broadcom.com>
> Signed-off-by: Michael Chan <michael.chan@broadcom.com>
> ---
> drivers/net/ethernet/broadcom/bnxt/bnxt.c | 7 ++++---
> 1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/net/ethernet/broadcom/bnxt/bnxt.c b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> index 619eb55..8eb73fe 100644
> --- a/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> +++ b/drivers/net/ethernet/broadcom/bnxt/bnxt.c
> @@ -11779,6 +11779,10 @@ static void bnxt_remove_one(struct pci_dev *pdev)
> if (BNXT_PF(bp))
> bnxt_sriov_disable(bp);
>
> + clear_bit(BNXT_STATE_IN_FW_RESET, &bp->state);
> + bnxt_cancel_sp_work(bp);
> + bp->sp_event = 0;
> +
> bnxt_dl_fw_reporters_destroy(bp, true);
> if (BNXT_PF(bp))
> devlink_port_type_clear(&bp->dl_port);
> @@ -11786,9 +11790,6 @@ static void bnxt_remove_one(struct pci_dev *pdev)
> unregister_netdev(dev);
> bnxt_dl_unregister(bp);
> bnxt_shutdown_tc(bp);
> - clear_bit(BNXT_STATE_IN_FW_RESET, &bp->state);
> - bnxt_cancel_sp_work(bp);
> - bp->sp_event = 0;
>
> bnxt_clear_int_mode(bp);
> bnxt_hwrm_func_drv_unrgtr(bp);
devlink can itself scheduler a recovery via:
bnxt_fw_fatal_recover() -> bnxt_fw_reset()
no? Maybe don't make the devlink recovery path need to go via a
workqueue?
next prev parent reply other threads:[~2020-09-06 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-06 2:55 [PATCH net 0/2] bnxt_en: Two bug fixes Michael Chan
2020-09-06 2:55 ` [PATCH net 1/2] bnxt_en: Avoid sending firmware messages when AER error is detected Michael Chan
2020-09-06 2:55 ` [PATCH net 2/2] bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task() Michael Chan
2020-09-06 19:25 ` Jakub Kicinski [this message]
2020-09-06 22:07 ` Michael Chan
2020-09-07 3:13 ` Jakub Kicinski
2020-09-07 3:48 ` Michael Chan
2020-09-07 17:13 ` Jakub Kicinski
2020-09-07 17:16 ` [PATCH net 0/2] bnxt_en: Two bug fixes Jakub Kicinski
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=20200906122534.54e16e08@kicinski-fedora-pc1c0hjn.dhcp.thefacebook.com \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=vasundhara-v.volam@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).