On Mon, 2014-10-27 at 21:10 +0100, Julien Cristau wrote: > On Mon, Oct 27, 2014 at 13:40:44 +0000, Ben Hutchings wrote: > > > I've now written and tested patches for that remaining regression. > > > > Source at: > > https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.dsc > > https://people.debian.org/~benh/packages/linux_3.2.63-2+deb7u1.debian.tar.xz > > > > Binary at: > > https://people.debian.org/~benh/packages/linux-image-3.2.0-4-amd64_3.2.63-2+deb7u1_amd64.deb > > > > There's a signed .changes file there as well, for verification > > (distribution=UNRELEASED in case you are wondering). > > > > Additional testing would be appreciated. > > > Installed your package on salieri.debian.org now. Anything we should > look out for?
1. It shouldn't crash, obviously.
2. You may see a one-time warning about using UFO when we don't claim to
support it, until you also upgrade the guest kernels. I found that
libvirt+QEMU tells guests they can use UFO even if the host tap device
refuses to support it.
3. UDP packets from the guest that require fragmentation should each get
a different fragmentation ID, and if they are sent at a low rate, the
IDs should not be consecutive (that was the purpose of the change in
3.2.63). You can check this by capturing and dumping IPv6 fragments on
a *remote* machine:
tcpdump -i eth0 -v 'ip6[6]==44'
Example output:
21:33:12.522227 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag (0x0276214b:0|1448)
32794 > discard: UDP, length 10240
21:33:12.522271 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:1448|1448)
21:33:12.522282 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:2896|1448)
21:33:12.522293 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:4344|1448)
21:33:12.522301 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:5792|1448)
21:33:12.522312 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:7240|1448)
21:33:12.522322 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:8688|1448)
21:33:12.522334 IP6 (hlim 64, next-header Fragment (44) payload length: 120)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276214b:10136|112)
21:33:13.231373 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag (0x0276218f:0|1448)
59424 > discard: UDP, length 10240
21:33:13.231414 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:1448|1448)
21:33:13.231424 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:2896|1448)
21:33:13.231432 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:4344|1448)
21:33:13.231441 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:5792|1448)
21:33:13.231450 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:7240|1448)
21:33:13.231460 IP6 (hlim 64, next-header Fragment (44) payload length: 1456)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:8688|1448)
21:33:13.231472 IP6 (hlim 64, next-header Fragment (44) payload length: 120)
fe80::5604:a6ff:fec4:8ddd > fe80::2a92:4aff:fe2f:b2d: frag
(0x0276218f:10136|112)
The first number after 'frag' is the fragmentation ID; here there are
two sets of fragments from two original 10K packets.
This should work whether or not the guest kernel is upgraded.
Ben.
--
Ben Hutchings
Theory and practice are closer in theory than in practice.
- John Levine, moderator of comp.compilers
signature.asc
Description: This is a digitally signed message part
