mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Gustavo Luiz Duarte <gustavold@gmail.com>
Cc: Breno Leitao <leitao@debian.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net v3 0/2] netconsole: fix target enable race and configfs read locking
Date: Fri, 16 Oct 2026 18:51:02 -0700	[thread overview]
Message-ID: <20261016185102.19cf818b@kernel.org> (raw)
In-Reply-To: <20261012-netcons-fixes-v3-0-1aac85ed7665@gmail.com>

On Mon, 12 Oct 2026 17:41:56 +0100 Gustavo Luiz Duarte wrote:
> While looking into the sashiko report about local_ip_show() and
> remote_ip_show() missing proper locking [1], I noticed a couple other
> places that need locking: patch 1/2 fixes a null-ptr-deref when enabling
> a target races against a NETDEV_UNREGISTER event, and patch 2/2 fixes a
> use-after-free when the local_mac_show() callback races against a
> NETDEV_UNREGISTER event.

Clashiko reports one more pre-existing race, we should probably 
address in the same series:
https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20261012-netcons-fixes-v3-1-1aac85ed7665@gmail.com
-- 
pw-bot: cr

      parent reply	other threads:[~2026-10-17  1:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 16:41 Gustavo Luiz Duarte
2026-10-12 16:41 ` [PATCH net v3 1/2] netconsole: finish enabling the target before releasing RTNL Gustavo Luiz Duarte
2026-10-12 16:41 ` [PATCH net v3 2/2] netconsole: read np.dev under target_list_lock in local_mac_show() Gustavo Luiz Duarte
2026-10-17  1:51 ` Jakub Kicinski [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=20261016185102.19cf818b@kernel.org \
    --to=kuba@kernel.org \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@kernel.org \
    --cc=gustavold@gmail.com \
    --cc=leitao@debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=stephen@networkplumber.org \
    /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®