Bug#854348: ipv6: refcnt pb when removing a peer address

Le 20/04/2017 à 00:15, Ben Hutchings a écrit : > On Mon, 2017-02-06 at 11:09 +0100, Nicolas Dichtel wrote: >> Package: src:linux >> Version: 3.16.39-1 >> Severity: important >> Tags: patch >> >> Dear Maintainer, >> >> Under some circumstances

Bug#854348: ipv6: refcnt pb when removing a peer address

Package: src:linux Version: 3.16.39-1 Severity: important Tags: patch Dear Maintainer, Under some circumstances, when an ipv6 peer addresse is removed, there is a refcnt problem: kernel:[ 9614.220549] unregister_netdevice: waiting for lo to become free. Usage count = 2 This bug has been fixed

Bug#813601: closed by Ben Hutchings (Re: linux-image-3.16: kernel panic when umounting rootfs)

Le 04/02/2016 11:19, Nicolas Dichtel a écrit : Le 04/02/2016 05:24, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the src:linux package: #813601: linux-image-3.16: kernel panic when umounting rootfs It has been closed

Bug#813601: closed by Ben Hutchings (Re: linux-image-3.16: kernel panic when umounting rootfs)

Le 04/02/2016 05:24, Debian Bug Tracking System a écrit : This is an automatic notification regarding your Bug report which was filed against the src:linux package: #813601: linux-image-3.16: kernel panic when umounting rootfs It has been closed by Ben Hutchings . I've misread the commit log.

Bug#813616: linux-image-3.16: namespaces: the syscall setns() is too slow

Package: src:linux Version: 3.16.7-ckt11-1+deb8u6 Severity: important Tags: patch Dear Maintainer, These upstream patches are missing: 3d93116cef30 fs/proc_namespace.c: simplify testing nsp and nsp->mnt_ns 728dba3a39c6 namespaces: Use task_lock and not rcu to protect nsproxy http://git.kernel.or

Bug#813601: linux-image-3.16: kernel panic when umounting rootfs

Package: src:linux Version: 3.16.7-ckt11-1+deb8u6 Severity: critical Tags: patch Justification: breaks the whole system Dear Maintainer, This upstream commit is missing: da362b09e42e umount: Do not allow unmounting rootfs. http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=

Bug#813594: linux-image-3.16: ip6_vti is broken

Package: src:linux Version: 3.16.7-ckt11-1+deb8u6 Severity: important Tags: patch ipv6 Dear Maintainer, The following upstream patches are missing: d55c670cbc54 ip_vti/ip6_vti: Preserve skb->mark after rcv_cb call 049f8e2e28d9 xfrm: Override skb->mark with tunnel->parm.i_key in xfrm_input cd5279c

Bug#808213: Info received (Bug#808213: libnl3: socket is unusable when portid generation fails)

Le 25/01/2016 09:45, Heiko Stübner a écrit : sorry about dropping the ball here, it somehow got pushed under in january- madness. Looks like I'm through now though, so expect packages today or tomorrow. No problem, thank you for the news. Regards, Nicolas

Bug#808213: Info received (Bug#808213: libnl3: socket is unusable when portid generation fails)

Any news about the update to the libnl 3.2.27? It would be nice if the new package would be available for the next ubuntu release (16.04). Thank you, Nicolas Le 17/12/2015 14:24, Debian Bug Tracking System a écrit : Thank you for the additional information you have supplied regarding this Bug

Bug#812102: Acknowledgement (iproute2: Segmentation fault with 'ip link set')

To reproduce it: root@bretzel:~# ip -f inet6 tunnel add gre2 mode ip6gre local fd00:125::1:1 remote fd00:125::1:2 dev eth0 root@bretzel:~# ip link set gre2 type ip6gre hoplimit 32 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: message exceeded bound of 1024 addattr_l ERROR: me

Bug#812102: iproute2: Segmentation fault with 'ip link set'

Package: iproute2 Version: 3.16.0-2 Severity: important Tags: patch The following upstream patch fixes this issue: https://git.kernel.org/cgit/linux/kernel/git/shemminger/iproute2.git/commit/?id=ed108cfc0260b6b751647982b77d6363b1defb15 It is included in iproute2 4.4. -- System Information: Debia

Bug#808213: libnl3: socket is unusable when portid generation fails

Hi Heiko, Le 17/12/2015 13:32, Heiko Stübner a écrit : Hi Nicolas, thanks for your report Am Donnerstag, 17. Dezember 2015, 11:30:57 schrieben Sie: Package: libnl-3-200 Version: 3.2.24-2 not sure, but I guess you meant 3.2.26-1, right? Yes (it's the first time I use bugreport ;-)). S

Bug#808213: Backport on libnl 3.2.26

I forget to mention that I can do the backport of these three patches over the libnl 3.2.26 if updating to libnl 3.2.27 is not possible. Regards, Nicolas

Bug#808213: libnl3: socket is unusable when portid generation fails

Package: libnl-3-200 Version: 3.2.24-2 Severity: important Tags: patch The following upstream patches are missing in libnl 3.2.26 (the unstable version): - f78c3e82398a socket: clear port when unable to generate local port https://github.com/thom311/libnl/commit/f78c3e82398a - 96e1e5bdc2e8 socke