[dpdk-dev] [Bug 864] [dpdk-21.11]pmd_stacked_bonded/test_mode_backup_rx:after setup stacked bonded ports, start top level bond port failed

[dpdk-dev] [Bug 864] [dpdk-21.11]pmd_stacked_bonded/test_mode_backup_rx:after setup stacked bonded ports, start top level bond port failed

[bugzilla]

https://bugs.dpdk.org/show_bug.cgi?id=864

            Bug ID: 864
           Summary: [dpdk-21.11]pmd_stacked_bonded/test_mode_backup_rx:aft
                    er setup stacked bonded ports,start top level bond
                    port failed
           Product: DPDK
           Version: 21.11
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Severity: normal
          Priority: Normal
         Component: core
          Assignee: dev@dpdk.org
          Reporter: leweix.yang@intel.com
  Target Milestone: ---

DPDK version: Use make showversion or for a non-released version: git remote -v
&& git show-ref --heads
 21.11-rc1:6c390cee976e33b1e9d8562d32c9d3ebe5d9ce94
Other software versions: name/version for QEMU, OVS, etc. Repeat as required.
OS: Red Hat Enterprise Linux 8.4 4.18.0-305.19.1.el8_4.x86_64 
Compiler: gcc (GCC) 8.4.1 20200928 (Red Hat 8.4.1-1)
Hardware platform: Intel(R) Xeon(R) Gold 6252N CPU @ 2.30GHz.
NIC hardware: Ethernet Controller XXV710 for 25GbE SFP28 158b
NIC firmware: 8.30 0x8000a485 1.2926.0
Device version: 2.17.1


Test Setup
Steps to reproduce
List the steps to reproduce the issue.

1.build dpdk 
# CC=gcc meson -Denable_kmods=True -Dlibdir=lib  --default-library=static
x86_64-native-bsdapp-gcc
# ninja -C x86_64-native-bsdapp-gcc
2.lanch app
# x86_64-native-linuxapp-gcc/app/dpdk-testpmd -l
1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,49,50,51,52,53,54,55,56,57,58,59,60,61,62,63,64,65,66,67,68,69,70,71
-n 4 -a 0000:af:00.0 -a 0000:af:00.1 --file-prefix=dpdk_875252_20211027094057 –
-i
3.execute dpdk command 
# port stop all
# create bonded device 1 1
# add bonding slave 0 2
# create bonded device 1 1
# add bonding slave 1 3
# create bonded device 1 1
# add bonding slave 2 4
# add bonding slave 3 4
# set portlist 0,1,2,3,4
# port start 4



Show the output from the previous commands:

# testpmd>port start 4
Configuring Port 4 (socket 1)
Device with port_id=2 already stopped
Port 2 must be configured before MTU set
slave_configure(1741) - rte_eth_dev_set_mtu: port 2, err (-22)
bond_ethdev_start(1994) - bonded port (4) failed to reconfigure slave device
(2)
Fail to start port 4: Operation not permitted
Please stop the ports first
Done
testpmd>



Expected Result
Explain what is the expected result in text or as an example output:

# execute success
Regression
Is this issue a regression: (Y/N) Y

git show b26bee10ee37ac2e54011f7bd57ca806bd9f8f6c
commit b26bee10ee37ac2e54011f7bd57ca806bd9f8f6c
Author: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
Date: Fri Oct 22 13:18:28 2021 +0300

ethdev: forbid MTU set before device configure

rte_eth_dev_configure() always sets MTU to either dev_conf.rxmode.mtu
or RTE_ETHER_MTU if application doesn't provide the value.
So, there is no point to allow rte_eth_dev_set_mtu() before since
set value will be overwritten on configure anyway.

Fixes: 1bb4a528c41f ("ethdev: fix max Rx packet length")

Signed-off-by: Ivan Ilchenko <ivan.ilchenko@oktetlabs.ru>
Signed-off-by: Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>
Reviewed-by: Ferruh Yigit <ferruh.yigit@intel.com>

-- 
You are receiving this mail because:
You are the assignee for the bug.