public inbox for linux-rdma@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Gunthorpe <jgg@nvidia.com>
To: Selvin Xavier <selvin.xavier@broadcom.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org,
	Naresh Kumar PBS <nareshkumar.pbs@broadcom.com>,
	Devesh Sharma <devesh.sharma@broadcom.com>
Subject: Re: [PATCH for-next v2] RDMA/bnxt_re: Move device to error state upon device crash
Date: Fri, 26 Mar 2021 11:03:08 -0300	[thread overview]
Message-ID: <20210326140308.GA839155@nvidia.com> (raw)
In-Reply-To: <1615968942-30970-1-git-send-email-selvin.xavier@broadcom.com>

On Wed, Mar 17, 2021 at 01:15:42AM -0700, Selvin Xavier wrote:
> When L2 driver detects a device crash or device undergone
> reset, it invokes a stop callback to recover from error.
> Current RoCE driver doesn't recover the device. So move
> the device to error state and dispatch fatal events to all qps
> Release the MSIx vectors to avoid a crash when  L2 driver
> disables the MSIx.
> Also, check for the device state to avoid posting further
> commands to the HW.
> 
> Signed-off-by: Naresh Kumar PBS <nareshkumar.pbs@broadcom.com>
> Signed-off-by: Devesh Sharma <devesh.sharma@broadcom.com>
> Signed-off-by: Selvin Xavier <selvin.xavier@broadcom.com>
> ---
> v1->v2:
> Fix the build warning
> Reported-by: kernel test robot <lkp@intel.com>

Applied to for-next

> +	bnxt_re_dev_stop(rdev);
> +	bnxt_re_stop_irq(rdev);
> +	/* Move the device states to detached and  avoid sending any more
> +	 * commands to HW
> +	 */
> +	set_bit(BNXT_RE_FLAG_ERR_DEVICE_DETACHED, &rdev->flags);
> +	set_bit(ERR_DEVICE_DETACHED, &rdev->rcfw.cmdq.flags);

But I'm skeptical that all this set_bit stuff without any locks in the
driver is sane

Jason

      reply	other threads:[~2021-03-26 14:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-17  8:15 [PATCH for-next v2] RDMA/bnxt_re: Move device to error state upon device crash Selvin Xavier
2021-03-26 14:03 ` Jason Gunthorpe [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=20210326140308.GA839155@nvidia.com \
    --to=jgg@nvidia.com \
    --cc=devesh.sharma@broadcom.com \
    --cc=dledford@redhat.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=nareshkumar.pbs@broadcom.com \
    --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