From: Tobias Hommel <netdev-list@genoetigt.de>
To: Kristian Evensen <kristian.evensen@gmail.com>
Cc: Steffen Klassert <steffen.klassert@secunet.com>,
Markus Berner <Markus.Berner@gmx.ch>,
Network Development <netdev@vger.kernel.org>
Subject: Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup
Date: Wed, 6 Jun 2018 18:03:19 +0200 [thread overview]
Message-ID: <20180606160318.cg556jqobvd5z3ja@delI> (raw)
In-Reply-To: <CAKfDRXhHMg5HKX=T1BKs5mx+BL-L8VyzqApS+8E52mDipZzU6Q@mail.gmail.com>
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 7-8 hours. My setup is nothing crazy, between 7 and 20
> tunnels with heavy RX/TX.
>
> On Fri, Feb 2, 2018 at 9:09 AM, Steffen Klassert
> <steffen.klassert@secunet.com> wrote:
> > Thanks for offering help, but I fear we have to wait until
> > Tobias has bisected it.
>
> Has any progress been made here? I would like to try a bisect myself,
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.
> but my board is running OpenWRT, which makes bisecting hard. The only
> observation I have so far, is that I did not see the issue with kernel
> 4.9.
>
> BR,
> Kristian
Tobi
next prev parent reply other threads:[~2018-06-06 16:09 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 21:13 BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup Tobias Hommel
2018-01-05 21:27 ` Ozgur
2018-01-05 21:55 ` Tobias Hommel
2018-01-08 8:57 ` Tobias Hommel
2018-01-08 12:38 ` Steffen Klassert
2018-01-05 21:51 ` Holger Hoffstätte
2018-01-05 22:40 ` Tobias Hommel
2018-01-08 12:36 ` Steffen Klassert
2018-01-08 13:53 ` Tobias Hommel
2018-01-09 8:19 ` Steffen Klassert
2018-01-09 9:06 ` Tobias Hommel
2018-01-09 9:26 ` Steffen Klassert
2018-01-09 14:49 ` Tobias Hommel
2018-01-10 7:30 ` Steffen Klassert
2018-01-10 9:03 ` Tobias Hommel
2018-01-19 14:45 ` Tobias Hommel
2018-01-24 9:59 ` Steffen Klassert
2018-01-29 8:38 ` Tobias Hommel
2018-01-31 20:26 ` Markus Berner
2018-02-02 8:09 ` Steffen Klassert
2018-06-06 10:41 ` Kristian Evensen
2018-06-06 10:58 ` Kristian Evensen
2018-06-06 16:03 ` Tobias Hommel [this message]
2018-06-08 8:41 ` Kristian Evensen
2018-06-12 8:03 ` Steffen Klassert
2018-06-12 8:29 ` Kristian Evensen
2018-06-14 8:38 ` Kristian Evensen
2018-09-06 13:03 ` Tobias Hommel
2018-06-12 18:39 ` Tobias Hommel
2018-01-10 7:42 ` Tobias Hommel
2018-01-10 7:50 ` Steffen Klassert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180606160318.cg556jqobvd5z3ja@delI \
--to=netdev-list@genoetigt.de \
--cc=Markus.Berner@gmx.ch \
--cc=kristian.evensen@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=steffen.klassert@secunet.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox