The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Hangbin Liu <hangbin.liu@linux.dev>
To: Jay Vosburgh <jv@jvosburgh.net>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Hangbin Liu <liuhangbin@kylinos.cn>
Subject: Re: [PATCH 0/2] bonding: 3ad: fix 2 RCU issues in ad_mux_machine()
Date: Thu, 20 Aug 2026 17:09:04 +0800	[thread overview]
Message-ID: <aobEMA3NRBt7YVMt@fedora> (raw)
In-Reply-To: <20260817-bond_rcu-v1-0-acf067cf45fe@kylinos.cn>

Hi,

On Mon, Aug 17, 2026 at 04:32:35PM +0800, Hangbin Liu wrote:
> This series addresses a NULL pointer dereference in ad_mux_machine()
> when ad_port_selection_logic() detaches a port from its aggregator
> but does not assign a replacement.
> 
> Patch 1 adds an early null aggregator check in ad_mux_machine() to
> prevent the oops. Patch 2 is a minor RCU fix that uses RCU_INIT_POINTER()
> when initializing port->aggregator to NULL.

Please ignore this patch set. I just got back to upstream after a few months'
leave and didn't catch up with the new policy before sending this series.

The first patch is only theoretical and has no reproducer. The second patch
is a NOP, as Eric said. So let's drop this patch set.

Thanks
Hangbin

      parent reply	other threads:[~2026-08-20  9:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-17  8:32 [PATCH 0/2] bonding: 3ad: fix 2 RCU issues in ad_mux_machine() Hangbin Liu
2026-08-17  8:32 ` [PATCH 1/2] bonding: 3ad: fix NULL pointer dereference " Hangbin Liu
2026-08-17  8:32 ` [PATCH 2/2] bonding: 3ad: use RCU_INIT_POINTER for rcu pointer initialization Hangbin Liu
2026-08-17  8:37   ` Eric Dumazet
2026-08-17  9:23     ` Hangbin Liu
2026-08-20  9:09 ` Hangbin Liu [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=aobEMA3NRBt7YVMt@fedora \
    --to=hangbin.liu@linux.dev \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=jv@jvosburgh.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuhangbin@kylinos.cn \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.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