Commit a660471
eth: bnxt: do not use BNXT_VNIC_NTUPLE unconditionally in queue restart logic
[ Upstream commit 6619585 ]
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: Sasha Levin <sashal@kernel.org>1 parent 14eb5f0 commit a660471
1 file changed
+2
-2
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
15287 | 15287 | | |
15288 | 15288 | | |
15289 | 15289 | | |
15290 | | - | |
| 15290 | + | |
15291 | 15291 | | |
15292 | 15292 | | |
15293 | 15293 | | |
| |||
15315 | 15315 | | |
15316 | 15316 | | |
15317 | 15317 | | |
15318 | | - | |
| 15318 | + | |
15319 | 15319 | | |
15320 | 15320 | | |
15321 | 15321 | | |
| |||
0 commit comments