summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2026-07-21 11:18:57 -0700
committerJakub Kicinski <kuba@kernel.org>2026-07-21 11:18:57 -0700
commite372a49cb81a7c24c48b935cf75e550d1f8750f6 (patch)
tree024933fcc1a4492d7a842a92fe2795808aea204e /tools/perf/scripts/python
parentede0f99cef53ae142ec9f54c705e4b1e48355fd3 (diff)
parent569595dc92e05a03083287adce9c58dd3ddb16a0 (diff)
Merge branch 'net-fix-stale-tx-skb-pointers-on-dma-map-failure'
Xuanqiang Luo says: ==================== net: fix stale TX skb pointers on DMA map failure From: Xuanqiang Luo <luoxuanqiang@kylinos.cn> While I was backporting commit 1a303baa715e6 ("ice: fix double-free of tx_buf skb"), an AI-assisted scan identified several suspected TX error paths. I reviewed the results and found this issue in the three drivers fixed here. The drivers differ, but the bug is the same. On a DMA mapping failure, the TX path frees an skb while its ring entry still points to it. A later transmission normally overwrites the entry. If the interface is stopped first, teardown can instead access or free the skb again. I do not have these adapters, so I have not tested the drivers on hardware. I checked the error and teardown paths by inspection. Still, these small fixes seem worth posting for review. They are independent, but are sent as one series because they address the same issue. ==================== Link: https://patch.msgid.link/20260710090527.58354-1-xuanqiang.luo@linux.dev Signed-off-by: Jakub Kicinski <kuba@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions