aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/util/scripting-engines/trace-event-python.c
diff options
context:
space:
mode:
authorPaolo Abeni <[email protected]>2024-08-16 17:20:34 +0200
committerJakub Kicinski <[email protected]>2024-08-20 15:46:52 -0700
commit8aba27c4a5020abdf60149239198297f88338a8d (patch)
treef6c2d03fd4a12c2e9449660139605aaf5604b41c /tools/perf/util/scripting-engines/trace-event-python.c
parent80a1e7b83bb1834b5568a3872e64c05795d88f31 (diff)
igb: cope with large MAX_SKB_FRAGS
Sabrina reports that the igb driver does not cope well with large MAX_SKB_FRAG values: setting MAX_SKB_FRAG to 45 causes payload corruption on TX. An easy reproducer is to run ssh to connect to the machine. With MAX_SKB_FRAGS=17 it works, with MAX_SKB_FRAGS=45 it fails. This has been reported originally in https://bugzilla.redhat.com/show_bug.cgi?id=2265320 The root cause of the issue is that the driver does not take into account properly the (possibly large) shared info size when selecting the ring layout, and will try to fit two packets inside the same 4K page even when the 1st fraglist will trump over the 2nd head. Address the issue by checking if 2K buffers are insufficient. Fixes: 3948b05950fd ("net: introduce a config option to tweak MAX_SKB_FRAGS") Reported-by: Jan Tluka <[email protected]> Reported-by: Jirka Hladky <[email protected]> Reported-by: Sabrina Dubroca <[email protected]> Tested-by: Sabrina Dubroca <[email protected]> Tested-by: Corinna Vinschen <[email protected]> Signed-off-by: Paolo Abeni <[email protected]> Signed-off-by: Corinna Vinschen <[email protected]> Link: https://patch.msgid.link/[email protected] Signed-off-by: Jakub Kicinski <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions