Hi, On Wed Oct 22, 2014 at 01:02:07 +0100, Ben Hutchings wrote: > I think this is the upstream change which would fix this. Please test > this on top of the previous one, in case there are any more cases where > ipv6_select_ident() may be called with a rt == NULL. > > However, it seems that with this change, when a VM offloads UDP/IPv6 > fragmentation to us, we will always set the fragmentation ID to 0. I'm > not sure whether that's a regression from 3.2.62, but I think it is. We > should not be choosing fragment IDs for VMs, but currently they aren't > telling us what to use! I've queried this upstream.
i have build a new kernel with the above mentioned patches applied. This package is now available on https://people.debian.org/~zobel/linux-image-3.2.0-4-amd64_3.2.63-2a~test_amd64.deb Both machines that i installed the kernel on run for quite some time without any issue now. Before those patches they stayed up only for a few minutes. Cheers, Martin -- Martin Zobel-Helas <zo...@debian.org> Debian System Administrator Debian & GNU/Linux Developer Debian Listmaster http://about.me/zobel Debian Webmaster GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20141023141618.ga31...@ftbfs.de
