All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Kevin Berry <kpberry@google.com>
Cc: xmei5@asu.edu, bestswngs@gmail.com, chenglongtang@google.com,
	joneslee@google.com, pabeni@redhat.com, rnj@google.com,
	stable@vger.kernel.org, Sasha Levin <sashal@kernel.org>
Subject: Re: [PATCH] net: bonding: fix use-after-free in bond_xmit_broadcast()
Date: Tue, 16 Jun 2026 12:18:56 +0530	[thread overview]
Message-ID: <2026061640-crunchy-patio-be38@gregkh> (raw)
In-Reply-To: <CAMAJAJG3Ox-GPz+t05On6F6pJt5rFAvo2AcMW9jJmG1O4EGOLA@mail.gmail.com>

On Tue, Jun 16, 2026 at 02:41:37AM -0400, Kevin Berry wrote:
> > That worked, thanks!
> >
> > greg k-h
> 
> Glad to hear it!
> 
> It's also worth pointing out that because the fix for 6.12 was done
> without the ce7a381697cb3 ("net: bonding: add broadcast_neighbor
> option for 802.3ad") dependency, it conflicts with the c4f050ce06c56
> ("bonding: 3ad: implement proper RCU rules for port->aggregator") fix
> commit series that was applied to other trees. So for 6.12, I think it
> would make sense to:
> 
> 1. Revert the fix from this thread: 3453882f36c4 ("net: bonding: fix
> use-after-free in bond_xmit_broadcast()"),
> 2. Apply the patch series for c4f050ce06c56 ("bonding: 3ad: implement
> proper RCU rules for port->aggregator"), namely:
>     - Apply 4440873f36553 ("bonding: 802.3ad replace MAC_ADDRESS_EQUAL
> with __agg_has_partner")
>     - Apply ce7a381697cb3 ("net: bonding: add broadcast_neighbor
> option for 802.3ad")
>     - Apply 6b6dc81ee7e8c ("bonding: add support for per-port LACP
> actor priority")
>     - Apply 4916f2e2f3fc9 ("bonding: print churn state via netlink")
>     - Apply c4f050ce06c56 ("bonding: 3ad: implement proper RCU rules
> for port->aggregator")
> 3. Apply Xiang's original fix commit: 2884bf72fb8f ("net: bonding: fix
> use-after-free in bond_xmit_broadcast()").
> 
> That should make things consistent between 6.1, 6.6., and 6.12 with
> respect to those two fixes.

Please send a patch series that does this to make sure I get it correct.

thanks,

greg k-h

  reply	other threads:[~2026-06-16  6:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20260428104138.reply-bonding-6.12@kernel.org>
2026-04-28 16:32 ` [PATCH v2] net: bonding: fix use-after-free in bond_xmit_broadcast() Kevin Berry
2026-04-28 22:41   ` Xiang Mei
2026-05-06 20:28     ` Kevin Berry
2026-05-06 20:28       ` [PATCH] " Kevin Berry
2026-05-19 18:44         ` Kevin Berry
2026-05-20 11:32           ` Greg Kroah-Hartman
2026-05-20 17:29             ` Kevin Berry
2026-05-20 18:00               ` Greg KH
2026-05-21  5:55                 ` Kevin Berry
2026-06-16  5:12         ` Greg Kroah-Hartman
2026-06-16  5:55           ` Kevin Berry
2026-06-16  6:03             ` Greg Kroah-Hartman
2026-06-16  6:41               ` Kevin Berry
2026-06-16  6:48                 ` Greg Kroah-Hartman [this message]
2026-06-16 15:56                   ` Kevin Berry
2026-04-13 21:54 [PATCH 6.12.y] " Xiang Mei
2026-04-27 18:42 ` Kevin Berry
2026-04-27 18:42   ` [PATCH] " Kevin Berry
2026-04-27 20:07     ` Xiang Mei
2026-04-27 21:06       ` Kevin Berry

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=2026061640-crunchy-patio-be38@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=bestswngs@gmail.com \
    --cc=chenglongtang@google.com \
    --cc=joneslee@google.com \
    --cc=kpberry@google.com \
    --cc=pabeni@redhat.com \
    --cc=rnj@google.com \
    --cc=sashal@kernel.org \
    --cc=stable@vger.kernel.org \
    --cc=xmei5@asu.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.