diff options
| author |   David S. Miller <davem@davemloft.net> | 2018-02-01 09:36:04 -0500 |
|---|---|---|
| committer | David S. Miller <davem@davemloft.net> | 2018-02-01 09:36:04 -0500 |
| commit | 26c26ab02c49e64dbac3a9f56806005bc9e8b914 (patch) | |
| tree | 0f9864224175e08f9570804f2be150f459cf37e8 /net/ipv4/tcp_bbr.c | |
| parent | Merge tag 'docs-4.16' of git://git.lwn.net/linux (diff) | |
| parent | bnx2x: disable GSO where gso_size is too big for hardware (diff) | |
| download | linux-dev-26c26ab02c49e64dbac3a9f56806005bc9e8b914.tar.xz linux-dev-26c26ab02c49e64dbac3a9f56806005bc9e8b914.zip | |
Merge branch 'bnx2x-disable-GSO-on-too-large-packets'
Daniel Axtens says:
====================
bnx2x: disable GSO on too-large packets
We observed a case where a packet received on an ibmveth device had a
GSO size of around 10kB. This was forwarded by Open vSwitch to a bnx2x
device, where it caused a firmware assert. This is described in detail
at [0].
Ultimately we want a fix in the core, but that is very tricky to
backport. So for now, just stop the bnx2x driver from crashing.
When net-next re-opens I will send the fix to the core and a revert
for this.
v4 changes:
- fix compilation error with EXPORTs (patch 1)
- only do slow test if gso_size is greater than 9000 bytes (patch 2)
Thanks,
Daniel
[0]: https://patchwork.ozlabs.org/patch/859410/
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/ipv4/tcp_bbr.c')
0 files changed, 0 insertions, 0 deletions