automatic DPDK test reports
 help / color / mirror / Atom feed
From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: shperetz@nvidia.com
Subject: |SUCCESS|dpdk-next-net|1bdf2b3c27| Intel-Testing
Date: 05 Nov 2025 11:34:50 -0800	[thread overview]
Message-ID: <e04965$5molc6@ORVIESA003-auth.jf.intel.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 3384 bytes --]


Test-Label: intel-Testing
Test-Status: SUCCESS
_Testing PASS_

DPDK git repo: dpdk-next-net
commit e04f75d0febccea81cf6ab17f7f7f8810690ee75
Author: Shani Peretz <shperetz@nvidia.com>
Date:   Wed Nov 5 20:01:35 2025 +0200

    net/bonding: fix MAC address propagation in 802.3ad mode
    
    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>

Testing Summary : 18 Case Done, 18 Successful, 0 Failures      

TestPlan:
	pf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/pf_smoke_test_plan.rst
	vf_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/vf_smoke_test_plan.rst
	virtio_smoke: http://git.dpdk.org/tools/dts/tree/test_plans/virtio_smoke_test_plan.rst

TestSuite:
	pf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_pf_smoke.py
	vf_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_vf_smoke.py
	virtio_smoke: http://git.dpdk.org/tools/dts/tree/tests/TestSuite_virtio_smoke.py


OS : Ubuntu 22.04.5 LTS       
Kernel : 6.8.0-40-generic         
GCC : 11.4.0-1ubuntu1~22.04.2        
NIC : Ethernet Controller E810-C for SFP         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| pf_smoke    | test_pf_jumbo_frames      | passed|
	| pf_smoke    | test_pf_rss               | passed|
	| pf_smoke    | test_pf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_rss               | passed|
	| vf_smoke    | test_vf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_jumbo_frames      | n/a   |
	| virtio_smoke| test_virtio_loopback      | passed|
	| virtio_smoke| test_virtio_pvp           | passed|
	+-------------+---------------------------+-------+


OS : Ubuntu 22.04.5 LTS       
Kernel : 5.15.0-119-generic         
GCC : 11.4.0-1ubuntu1~22.04.2        
NIC : Ethernet Controller XL710 for 40GbE QSFP+         
Target : x86_64-native-linuxapp-gcc      

	Test result details:
	+-------------+---------------------------+-------+
	| suite       | case                      | status|
	+-------------+---------------------------+-------+
	| asan_smoke  | test_rxtx_with_ASan_enable| passed|
	| pf_smoke    | test_pf_jumbo_frames      | passed|
	| pf_smoke    | test_pf_rss               | passed|
	| pf_smoke    | test_pf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_rss               | passed|
	| vf_smoke    | test_vf_tx_rx_queue       | passed|
	| vf_smoke    | test_vf_jumbo_frames      | n/a   |
	| virtio_smoke| test_virtio_loopback      | passed|
	| virtio_smoke| test_virtio_pvp           | passed|
	+-------------+---------------------------+-------+


DPDK STV team

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

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-05 19:34 sys_stv [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-11-04 21:37 sys_stv

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='e04965$5molc6@ORVIESA003-auth.jf.intel.com' \
    --to=sys_stv@intel.com \
    --cc=shperetz@nvidia.com \
    --cc=test-report@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).