summaryrefslogtreecommitdiffstats
path: root/net/tipc
diff options
context:
space:
mode:
authorDavid Gibson <david@gibson.dropbear.id.au>2015-04-23 06:43:05 +0200
committerDavid S. Miller <davem@davemloft.net>2015-04-23 17:42:19 +0200
commit4fce14820c1b0a3fd399719f970e0c3ae40dd270 (patch)
tree5510f91bcaa804fbdfa91b50a346a603b4c615e2 /net/tipc
parentnetdev_alloc_pcpu_stats: use less common iterator variable (diff)
downloadlinux-4fce14820c1b0a3fd399719f970e0c3ae40dd270.tar.xz
linux-4fce14820c1b0a3fd399719f970e0c3ae40dd270.zip
ibmveth: Fix off-by-one error in ibmveth_change_mtu()
AFAIK the PAPR document which defines the virtual device interface used by the ibmveth driver doesn't specify a specific maximum MTU. So, in the ibmveth driver, the maximum allowed MTU is determined by the maximum allocated buffer size of 64k (corresponding to one page in the common case) minus the per-buffer overhead IBMVETH_BUFF_OH (which has value 22 for 14 bytes of ethernet header, plus 8 bytes for an opaque handle). This suggests a maximum allowable MTU of 65514 bytes, but in fact the driver only permits a maximum MTU of 65513. This is because there is a < instead of an <= in ibmveth_change_mtu(), which only permits an MTU which is strictly smaller than the buffer size, rather than allowing the buffer to be completely filled. This patch fixes the buglet. Signed-off-by: David Gibson <david@gibson.dropbear.id.au> Acked-by: Thomas Falcon <tlfalcon@linux.vnet.ibm.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc')
0 files changed, 0 insertions, 0 deletions