diff options
author | 2025-04-28 15:58:56 -0700 | |
---|---|---|
committer | 2025-04-30 13:03:21 +0100 | |
commit | 9ab7a709c926c16b4433cf02d04fcbcf35aaab2b (patch) | |
tree | 1840008c967d97c7ac7962dda3662771262df867 /scripts/lib/kdoc/kdoc_output.py | |
parent | net: ipv6: fix UDPv6 GSO segmentation with NAT (diff) | |
download | wireguard-linux-9ab7a709c926c16b4433cf02d04fcbcf35aaab2b.tar.xz wireguard-linux-9ab7a709c926c16b4433cf02d04fcbcf35aaab2b.zip |
bnxt_en: Fix error handling path in bnxt_init_chip()
WARN_ON() is triggered in __flush_work() if bnxt_init_chip() fails
because we call cancel_work_sync() on dim work that has not been
initialized.
WARNING: CPU: 37 PID: 5223 at kernel/workqueue.c:4201 __flush_work.isra.0+0x212/0x230
The driver relies on the BNXT_STATE_NAPI_DISABLED bit to check if dim
work has already been cancelled. But in the bnxt_open() path,
BNXT_STATE_NAPI_DISABLED is not set and this causes the error
path to think that it needs to cancel the uninitalized dim work.
Fix it by setting BNXT_STATE_NAPI_DISABLED during initialization.
The bit will be cleared when we enable NAPI and initialize dim work.
Fixes: 40452969a506 ("bnxt_en: Fix DIM shutdown")
Suggested-by: Somnath Kotur <somnath.kotur@broadcom.com>
Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
Signed-off-by: Shravya KN <shravya.k-n@broadcom.com>
Signed-off-by: Michael Chan <michael.chan@broadcom.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_output.py')
0 files changed, 0 insertions, 0 deletions