aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/include/linux/connector.h
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2023-07-20 20:09:16 -0700
committerJakub Kicinski <kuba@kernel.org>2023-07-20 20:09:16 -0700
commit022add1d73f14f021e0e0aa91304b83ad7169398 (patch)
tree97eaeaaedfd419060ec1785752a2dc9e5a004c17 /include/linux/connector.h
parentMerge git://git.kernel.org/pub/scm/linux/kernel/git/netdev/net (diff)
parenteth: bnxt: handle invalid Tx completions more gracefully (diff)
downloadwireguard-linux-022add1d73f14f021e0e0aa91304b83ad7169398.tar.xz
wireguard-linux-022add1d73f14f021e0e0aa91304b83ad7169398.zip
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/20230710205611.1198878-1-kuba@kernel.org/ ==================== Link: https://lore.kernel.org/r/20230720010440.1967136-1-kuba@kernel.org Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'include/linux/connector.h')
0 files changed, 0 insertions, 0 deletions