patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Shani Peretz <shperetz@nvidia.com>
Cc: <dev@dpdk.org>, <stable@dpdk.org>,
	Chas Williams <3chas3@gmail.com>,
	"Min Hu (Connor)" <humin29@huawei.com>,
	Pawel Wodkowski <pawelwod@gmail.com>,
	Declan Doherty <declan.doherty@intel.com>
Subject: Re: [PATCH] net/bonding: fix MAC address propagation in 802.3ad mode
Date: Wed, 5 Nov 2025 11:03:31 -0800	[thread overview]
Message-ID: <20251105110331.1975b42a@phoenix> (raw)
In-Reply-To: <20251105180135.1181619-1-shperetz@nvidia.com>

On Wed, 5 Nov 2025 20:01:35 +0200
Shani Peretz <shperetz@nvidia.com> wrote:

> When changing the MAC address of a bonding device in 802.3ad mode,
> the new MAC was not propagated to the physical member NIC.
> This caused the physical NIC to drop all data packets sent to the
> new MAC address, resulting in connectivity loss.
> 
> It happens because the MAC update function only updated the
> LACP layer (actor.system) but not the physical NIC hardware MAC
> addresses.
> 
> This fix adds a call to rte_eth_dev_default_mac_addr_set() to update
> the hardware MAC on each member port.
> 
> Bugzilla ID: 1158
> Fixes: 46fb43683679 ("bond: add mode 4")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Shani Peretz <shperetz@nvidia.com>
> ---

Queued to next-net.
Modified patch to put check on oneline since max line length in DPDK is 100.

      reply	other threads:[~2025-11-05 19:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 18:01 Shani Peretz
2025-11-05 19:03 ` Stephen Hemminger [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=20251105110331.1975b42a@phoenix \
    --to=stephen@networkplumber.org \
    --cc=3chas3@gmail.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=humin29@huawei.com \
    --cc=pawelwod@gmail.com \
    --cc=shperetz@nvidia.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).