eth: bnxt: do not use BNXT_VNIC_NTUPLE unconditionally in queue restart logic
authorTaehee Yoo <ap420073@gmail.com>
Sun, 9 Mar 2025 13:42:14 +0000 (13:42 +0000)
committerJakub Kicinski <kuba@kernel.org>
Mon, 10 Mar 2025 20:31:11 +0000 (13:31 -0700)
commit661958552eda5bf64bfafb4821cbdded935f1f68
tree473a009ecf539fe5d3681aedbf346b6c7f9e7de7
parentca2456e073957781e1184de68551c65161b2bd30
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: b9d2956e869c ("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>
drivers/net/ethernet/broadcom/bnxt/bnxt.c