diff options
author | Jakub Kicinski <[email protected]> | 2023-07-20 20:09:16 -0700 |
---|---|---|
committer | Jakub Kicinski <[email protected]> | 2023-07-20 20:09:16 -0700 |
commit | 022add1d73f14f021e0e0aa91304b83ad7169398 (patch) | |
tree | 97eaeaaedfd419060ec1785752a2dc9e5a004c17 /net/switchdev/switchdev.c | |
parent | 59be3baa8dff271d48500e009622318badfc7140 (diff) | |
parent | 2b56b3d9924160d84c37d085628525666e3b1cea (diff) |
Merge branch 'eth-bnxt-handle-invalid-tx-completions-more-gracefully'
Jakub Kicinski says:
====================
eth: bnxt: handle invalid Tx completions more gracefully
bnxt trusts the events generated by the device which may lead to kernel
crashes. These are extremely rare but they do happen. For a while
I thought crashing may be intentional, because device reporting invalid
completions should never happen, and having a core dump could be useful
if it does. But in practice I haven't found any clues in the core dumps,
and panic_on_warn exists.
Series was tested by forcing the recovery path manually. Because of
how rare the real crashes are I can't confirm it works for the actual
device errors until it's been widely deployed.
v1: https://lore.kernel.org/all/[email protected]/
====================
Link: https://lore.kernel.org/r/[email protected]
Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'net/switchdev/switchdev.c')
0 files changed, 0 insertions, 0 deletions