Netdev Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Baptiste Covolato <baptiste@arista.com>
To: Michael Chan <michael.chan@broadcom.com>
Cc: David Christensen <drc@linux.vnet.ibm.com>,
	Michael Chan <mchan@broadcom.com>,
	Siva Reddy Kallam <siva.kallam@broadcom.com>,
	Prashant Sreedharan <prashant@broadcom.com>,
	Netdev <netdev@vger.kernel.org>, Daniel Stodden <dns@arista.com>
Subject: Re: rtnl_lock deadlock with tg3 driver
Date: Mon, 31 Aug 2020 12:20:32 -0700	[thread overview]
Message-ID: <CABb8VeGse3W=oawRp+12FGCRhwMMs=fY4rbwM6HVKJSc41RfPw@mail.gmail.com> (raw)
In-Reply-To: <CACKFLin0kKuckRf2b7CmoAM3UyzOQZo7fRUg0-9jT5p_LLAhTA@mail.gmail.com>

On Sun, Aug 30, 2020 at 9:58 PM Michael Chan <michael.chan@broadcom.com> wrote:
>
> On Fri, Aug 28, 2020 at 5:40 PM Baptiste Covolato <baptiste@arista.com> wrote:
> >
> > Hi David, Michael,
> >
> > I am contacting you because I'm experiencing an issue that seems to be
> > awfully close to what David attempted to fix related to the tg3 driver
> > infinite sleep while holding rtnl_lock
> > (https://lkml.org/lkml/2020/6/15/1122).
>
> David's remaining issue was tg3_reset_task() returning failure due to
> some hardware error.  This would leave the driver in a limbo state
> with netif_running() still true, but NAPI not enabled.  This can
> easily lead to a soft lockup with rtnl held when it tries to disable
> NAPI again.
>
> I think the proper fix is to close the device when tg3_reset_task()
> fails to bring it to a consistent state.  I haven't heard back from
> David in a while, so I will propose a patch to do this in the next
> day.
>
> Let's see if this patch will also work for you.  Thanks.


Thanks Michael. Looking forward to trying this patch out.

-- 
Baptiste Covolato

      reply	other threads:[~2020-08-31 19:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  0:40 Baptiste Covolato
2020-08-31  4:58 ` Michael Chan
2020-08-31 19:20   ` Baptiste Covolato [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='CABb8VeGse3W=oawRp+12FGCRhwMMs=fY4rbwM6HVKJSc41RfPw@mail.gmail.com' \
    --to=baptiste@arista.com \
    --cc=dns@arista.com \
    --cc=drc@linux.vnet.ibm.com \
    --cc=mchan@broadcom.com \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=prashant@broadcom.com \
    --cc=siva.kallam@broadcom.com \
    --subject='Re: rtnl_lock deadlock with tg3 driver' \
    /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

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).