[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CACKFLin=-9=2x0MFuRfXM1HwFQ7uZSZ4i0HymRZDBVKcnK73NA@mail.gmail.com>
Date: Sun, 6 Sep 2020 15:07:02 -0700
From: Michael Chan <michael.chan@...adcom.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: David Miller <davem@...emloft.net>,
Netdev <netdev@...r.kernel.org>,
Vasundhara Volam <vasundhara-v.volam@...adcom.com>
Subject: Re: [PATCH net 2/2] bnxt_en: Fix NULL ptr dereference crash in bnxt_fw_reset_task()
On Sun, Sep 6, 2020 at 12:25 PM Jakub Kicinski <kuba@...nel.org> wrote:
>
> devlink can itself scheduler a recovery via:
>
> bnxt_fw_fatal_recover() -> bnxt_fw_reset()
>
Yes, this is how it is initiated when we call devlink_health_report()
to report the error condition. From bnxt_fw_reset(), we use a
workqueue because we have to go through many states, requiring
sleeping/polling to transition through the states.
> no? Maybe don't make the devlink recovery path need to go via a
> workqueue?
Current implementation is going through a work queue.
Powered by blists - more mailing lists