Commit f6cad31
committed
eth: bnxt: do not use BNXT_VNIC_NTUPLE unconditionally in queue restart logic
JIRA: https://issues.redhat.com/browse/RHEL-107291
commit 6619585
Author: Taehee Yoo <ap420073@gmail.com>
Date: Sun Mar 9 13:42:14 2025 +0000
eth: bnxt: do not use BNXT_VNIC_NTUPLE unconditionally in queue restart logic
When a queue is restarted, it sets MRU to 0 for stopping packet flow.
MRU variable is a member of vnic_info[], the first vnic_info is default
and the second is ntuple.
Only when ntuple is enabled(ethtool -K eth0 ntuple on), vnic_info for
ntuple is allocated in init logic.
The bp->nr_vnics indicates how many vnic_info are allocated.
However bnxt_queue_{start | stop}() accesses vnic_info[BNXT_VNIC_NTUPLE]
regardless of ntuple state.
Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
Fixes: b9d2956 ("bnxt_en: stop packet flow during bnxt_queue_stop/start")
Signed-off-by: Taehee Yoo <ap420073@gmail.com>
Link: https://patch.msgid.link/20250309134219.91670-4-ap420073@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Signed-off-by: Michal Schmidt <mschmidt@redhat.com>1 parent c8828b7 commit f6cad31
1 file changed
+2
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
15800 | 15800 | | |
15801 | 15801 | | |
15802 | 15802 | | |
15803 | | - | |
| 15803 | + | |
15804 | 15804 | | |
15805 | 15805 | | |
15806 | 15806 | | |
| |||
15834 | 15834 | | |
15835 | 15835 | | |
15836 | 15836 | | |
15837 | | - | |
| 15837 | + | |
15838 | 15838 | | |
15839 | 15839 | | |
15840 | 15840 | | |
| |||
0 commit comments