On Wed, Oct 04, 2017 at 08:49:51AM +0100, James Chapman wrote: > On 3 October 2017 at 08:27, James Chapman <jchap...@katalix.com> wrote: > > On 2 October 2017 at 19:35, SviMik <svi...@gmail.com> wrote: > >> Hi, James! > >> > >> No, I'm suffering from kernel panics since I started using 4.x > >> kernels. > > It's interesting that you are seeing l2tp issues since switching to > > 4.x kernels. Are you able to try earlier kernels to find the latest > > version that works? I'm curious whether things broke at v3.15. > > It's possible that this may be fixed by a patch that is already > upstream and merged for v4.14. The fix is from Guillaume Nault: > > f3c66d4 l2tp: prevent creation of sessions on terminated tunnels > > If it's possible that the L2TP server may try to create a session in a > tunnel that is being closed, this bug would be exposed. > Yes, I think this patch is worth a try. In the case of sessions created on a dead tunnel, I wouldn't have expected the xmit path to even reach l2tp_xmit_skb() though (that's certainly possible, but the timing constraints look a bit hard to reach).
BTW, I started working on this issue a few days ago and came to the same conclusions as the ones you posted in your previous replies. Given that we were in line with the analysis, I've switched to the PPP bug reported by Beniamino (https://www.spinics.net/lists/netdev/msg458002.html). I'll move back to L2TP as soon as possible.
