On Fri, Jun 08, 2018 at 10:41:37AM +0200, Kristian Evensen wrote: > Hi, > > On Wed, Jun 6, 2018 at 6:03 PM, Tobias Hommel <netdev-l...@genoetigt.de> > wrote: > > Sorry no progress until now, I currently do not get time to have a deeper > > look > > into that. We're back to 4.1.6 right now. > > Thanks for letting me know. In the project I am currently involved in, > we unfortunately don't have the option of reverting the kernel, so we > are finding ways to live with the error. We have been looking into the > error a bit more, and have made the following observations: > > * First of all, as discussed earlier in the thread, the error is > triggered by dst_orig being NULL.
I spent quite some time again yesterday in trying to find a case where dst_orig can be NULL in xfrm_lookup(). I don't see how this can happen, so I fear we need a bisection on this.
