Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hey guys, I finally got some time to do a bisect and we narrowed the problem down to: b838d5e1c5b6e57b10ec8af2268824041e3ea911 is the first bad commit commit b838d5e1c5b6e57b10ec8af2268824041e3ea911 Author: Wei Wang Date: Sat Jun 17 10:42:32 2017 -0700 ipv4: mark DST_NOGC and remove the

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hello, On Tue, Jun 12, 2018 at 10:29 AM, Kristian Evensen wrote: > Thanks for spending time on this. I will see what I can manage in > terms of a bisect. Our last good kernel was 4.9, so at least it > narrows the scope down a bit compared to 4.4 or 4.1. I hope we might have got somewhere. While

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

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 > 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

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hi, On Tue, Jun 12, 2018 at 10:03 AM, Steffen Klassert wrote: > 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. Thanks for spending time on this. I will see

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

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 > 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

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hi, On Wed, Jun 6, 2018 at 6:03 PM, Tobias Hommel 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

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hi, On Wed, Jun 06, 2018 at 12:41:53PM +0200, Kristian Evensen wrote: > Hi, > > I am experiencing the same issue on a PC Engines APU2 running kernel > 4.14.34, both with and without hardware encryption. With hw. > encryption, the crash occurs within 2-4 hours. Without hw. encryption, > it takes

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Wed, Jun 6, 2018 at 12:41 PM, Kristian Evensen wrote: > Hi, > > I am experiencing the same issue on a PC Engines APU2 running kernel > 4.14.34, both with and without hardware encryption. With hw. > encryption, the crash occurs within 2-4 hours. Without hw. encryption, > it takes 7-8 hours. My

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

Hi, I am experiencing the same issue on a PC Engines APU2 running kernel 4.14.34, both with and without hardware encryption. With hw. encryption, the crash occurs within 2-4 hours. Without hw. encryption, it takes 7-8 hours. My setup is nothing crazy, between 7 and 20 tunnels with heavy RX/TX.

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Wed, Jan 31, 2018 at 09:26:51PM +0100, Markus Berner wrote: > > I'm running into a NULL pointer dereference after updating from Linux > 4.1.6 to > > 4.14.11 (see kernel log below). > > We are running into the same problem on our production machine, running > CoreOS 1576.5.0 Stable with the

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

> I'm running into a NULL pointer dereference after updating from Linux 4.1.6 to > 4.14.11 (see kernel log below). We are running into the same problem on our production machine, running CoreOS 1576.5.0 Stable with the 4.14.11 kernel on a KVM Cloud VM. It is not as easy to reproduce though in

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Wed, Jan 24, 2018 at 10:59:21AM +0100, Steffen Klassert wrote: > On Fri, Jan 19, 2018 at 03:45:46PM +0100, Tobias Hommel wrote: > > > > I tried to strip down the system configuration and was able to reproduce the > > problem with a minimal configuration: > > * ipsets are not used anymore > > *

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Fri, Jan 19, 2018 at 03:45:46PM +0100, Tobias Hommel wrote: > > I tried to strip down the system configuration and was able to reproduce the > problem with a minimal configuration: > * ipsets are not used anymore > * no firewall markings are used any longer > * iptables are "completely empty",

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Wed, Jan 10, 2018 at 08:30:38AM +0100, Steffen Klassert wrote: > On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote: > > > > I copied the config from my 4.14.12 sources to a fresh 4.13.16 source tree, > > ran > > `make olddefconfig` and built a new kernel. > > The kernel config is

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Wed, Jan 10, 2018 at 08:42:19AM +0100, Tobias Hommel wrote: > On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote: > > On Tue, Jan 09, 2018 at 10:26:24AM +0100, Steffen Klassert wrote: > > > On Tue, Jan 09, 2018 at 10:06:51AM +0100, Tobias Hommel wrote: > > > > > > > > > > You have

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote: > On Tue, Jan 09, 2018 at 10:26:24AM +0100, Steffen Klassert wrote: > > On Tue, Jan 09, 2018 at 10:06:51AM +0100, Tobias Hommel wrote: > > > > > > > > You have CONFIG_INET_ESP_OFFLOAD enabled, this is new maybe it > > > > still has

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Tue, Jan 09, 2018 at 03:49:21PM +0100, Tobias Hommel wrote: > > I copied the config from my 4.14.12 sources to a fresh 4.13.16 source tree, > ran > `make olddefconfig` and built a new kernel. > The kernel config is attached as kernel-4.13.16.config. > The panic*.log files are kernel logs from

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Tue, Jan 09, 2018 at 10:06:51AM +0100, Tobias Hommel wrote: > > > > You have CONFIG_INET_ESP_OFFLOAD enabled, this is new maybe it > > still has some problems. You should not hit an offload codepath > > because all your SAs are configured with UDP encapsulation which > > is still not supported

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Tue, Jan 09, 2018 at 09:19:39AM +0100, Steffen Klassert wrote: > On Mon, Jan 08, 2018 at 02:53:48PM +0100, Tobias Hommel wrote: > > ... > > > [ 439.095554] BUG: unable to handle kernel NULL pointer dereference at > > 0020 > > [ 439.103664] IP: xfrm_lookup+0x2a/0x7d0 > > [

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Mon, Jan 08, 2018 at 02:53:48PM +0100, Tobias Hommel wrote: ... > [ 439.095554] BUG: unable to handle kernel NULL pointer dereference at > 0020 > [ 439.103664] IP: xfrm_lookup+0x2a/0x7d0 > [ 439.107551] PGD 0 P4D 0 > [ 439.110144] Oops: [#1] SMP PTI > [ 439.113653]

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Sat, Jan 06, 2018 at 12:27:11AM +0300, Ozgur wrote: > > > 06.01.2018, 00:20, "Tobias Hommel" : > > Hi, > > Hi Tobias, > > > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 > > to > > 4.14.11 (see kernel log below). I tried 4.14.3

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Fri, Jan 05, 2018 at 10:13:23PM +0100, Tobias Hommel wrote: > Hi, > > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 to > 4.14.11 (see kernel log below). I tried 4.14.3 initially which did not work > either. > Anyone has an idea what is happening here? > > The

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Fri, Jan 05, 2018 at 09:55:23PM +, Tobias Hommel wrote: > On Sat, Jan 06, 2018 at 12:27:11AM +0300, Ozgur wrote: > > > > > > 06.01.2018, 00:20, "Tobias Hommel" : > > > Hi, > > > > Hi Tobias, > > > > > I'm running into a NULL pointer dereference after updating

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Fri, Jan 05, 2018 at 09:51:16PM +, Holger Hoffstätte wrote: > On Fri, 05 Jan 2018 22:13:23 +0100, Tobias Hommel wrote: > > > Hi, > > > > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 > > to > > 4.14.11 (see kernel log below). I tried 4.14.3 initially which

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Fri, 05 Jan 2018 22:13:23 +0100, Tobias Hommel wrote: > Hi, > > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 to > 4.14.11 (see kernel log below). I tried 4.14.3 initially which did not work > either. > Anyone has an idea what is happening here? Try 4.14.12

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

On Sat, Jan 06, 2018 at 12:27:11AM +0300, Ozgur wrote: > > > 06.01.2018, 00:20, "Tobias Hommel" : > > Hi, > > Hi Tobias, > > > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 > > to > > 4.14.11 (see kernel log below). I tried 4.14.3

Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup

06.01.2018, 00:20, "Tobias Hommel" : > Hi, Hi Tobias, > I'm running into a NULL pointer dereference after updating from Linux 4.1.6 to > 4.14.11 (see kernel log below). I tried 4.14.3 initially which did not work > either. > Anyone has an idea what is happening here?