aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/s390/net
diff options
context:
space:
mode:
authorJakub Kicinski <kuba@kernel.org>2022-05-05 19:51:32 -0700
committerDavid S. Miller <davem@davemloft.net>2022-05-06 12:07:56 +0100
commit14d7b8122fd591693a2388b98563707ba72c6780 (patch)
tree63d32ba9fafbc94c643b44fb8dca44f98d2ce27a /drivers/s390/net
parentnet: add netif_inherit_tso_max() (diff)
downloadlinux-dev-14d7b8122fd591693a2388b98563707ba72c6780.tar.xz
linux-dev-14d7b8122fd591693a2388b98563707ba72c6780.zip
net: don't allow user space to lift the device limits
Up until commit 46e6b992c250 ("rtnetlink: allow GSO maximums to be set on device creation") the gso_max_segs and gso_max_size of a device were not controlled from user space. The quoted commit added the ability to control them because of the following setup: netns A | netns B veth<->veth eth0 If eth0 has TSO limitations and user wants to efficiently forward traffic between eth0 and the veths they should copy the TSO limitations of eth0 onto the veths. This would happen automatically for macvlans or ipvlan but veth users are not so lucky (given the loose coupling). Unfortunately the commit in question allowed users to also override the limits on real HW devices. It may be useful to control the max GSO size and someone may be using that ability (not that I know of any user), so create a separate set of knobs to reliably record the TSO limitations. Validate the user requests. Signed-off-by: Jakub Kicinski <kuba@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'drivers/s390/net')
0 files changed, 0 insertions, 0 deletions