lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 29 Oct 2016 23:01:04 -0400 (EDT) From: David Miller <davem@...emloft.net> To: stefanr@...6.in-berlin.de Cc: netdev@...r.kernel.org, linux1394-devel@...ts.sourceforge.net, jarod@...hat.com, linux-kernel@...r.kernel.org Subject: Re: [PATCH net-next] firewire: net: really fix maximum possible MTU From: Stefan Richter <stefanr@...6.in-berlin.de> Date: Sat, 29 Oct 2016 22:16:58 +0200 > The maximum unicast datagram size /without/ link fragmentation is > 4096 - 4 = 4092 (max IEEE 1394 async payload size at >= S800 bus speed, > minus unfragmented encapssulation header). Max broadcast datagram size > without fragmentation is 8 bytes less than that (due to GASP header). > > The maximum datagram size /with/ link fragmentation is 0xfff = 4095 > for unicast and broadcast. This is because the RFC 2734 fragment > encapsulation header field for datagram size is only 12 bits wide. > > Fixes: 5d48f00d836a('firewire: net: fix maximum possible MTU') > Signed-off-by: Stefan Richter <stefanr@...6.in-berlin.de> Applied, thanks.
Powered by blists - more mailing lists