mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <efault@gmx.de>
To: Florian Fainelli <florian.fainelli@broadcom.com>,
	lkml <linux-kernel@vger.kernel.org>
Cc: Doug Berger <opendmb@gmail.com>, Breno Leitao <leitao@debian.org>
Subject: Re: [patch] net, bcmgenet: Fix locking of netpoll facing functions
Date: Fri, 29 Aug 2025 04:40:54 +0200	[thread overview]
Message-ID: <1d439b1961a4f6b019e2cc56977e0860b3a7b937.camel@gmx.de> (raw)
In-Reply-To: <9b69b764-5691-4bcd-8784-eb657f13a3a4@broadcom.com>

On Thu, 2025-08-28 at 11:59 -0700, Florian Fainelli wrote:
> On 8/26/25 01:24, Mike Galbraith wrote:
> > Lockdep reports ring->lock to not be irq safe during netpoll/netconsole
> > session, resulting in a potential deadlock scenario.
> > 
> >   Chain exists of:
> >     &host->lock --> target_list_lock --> &ring->lock
> >    Possible interrupt unsafe locking scenario:
> >          CPU0                    CPU1
> >          ----                    ----
> >     lock(&ring->lock);
> >                                  local_irq_disable();
> >                                  lock(&host->lock);
> >                                  lock(target_list_lock);
> >     <Interrupt>
> >       lock(&host->lock);
> >    *** DEADLOCK ***
> > 
> > Prevent that via use of irqsave/restore spinlock variant when polling.
> > 
> > Signed-off-by: Mike Galbraith <efault@gmx.de>
> 
> Your patch did not make it to the adequate mailing list which should be 
> at least netdev@vger.kernel.org. This is effectively a partial revert of 
> b0447ecb533270cf857ebee1133cb8ff67115423 ("net: bcmgenet: relax lock 
> constraints to reduce IRQ latency") therefore I would want Doug to chime 
> in and review this.

Ah, just drop it, he'll likely do something way better.

	-Mike

      reply	other threads:[~2025-08-29  2:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-26  8:24 Mike Galbraith
2025-08-28 18:59 ` Florian Fainelli
2025-08-29  2:40   ` Mike Galbraith [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=1d439b1961a4f6b019e2cc56977e0860b3a7b937.camel@gmx.de \
    --to=efault@gmx.de \
    --cc=florian.fainelli@broadcom.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=opendmb@gmail.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

all inboxes | Powered by JetHome®