From: "Holger Hoffstätte" <holger@applied-asynchrony.com>
To: netdev@vger.kernel.org
Subject: Re: BUG: 4.14.11 unable to handle kernel NULL pointer dereference in xfrm_lookup
Date: Fri, 5 Jan 2018 21:51:16 +0000 (UTC) [thread overview]
Message-ID: <pan$a23bd$f3d36d79$5e2cceef$5e5c5076@applied-asynchrony.com> (raw)
In-Reply-To: 20180105211322.qykh5ct4g2eyp5rm@delI
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 because of:
https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git/commit/?h=linux-4.14.y&id=2d01ac8cc12b973668bf898b03bf9ffb12d83b83
-h
next prev parent reply other threads:[~2018-01-05 22:02 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 [this message]
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
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='pan$a23bd$f3d36d79$5e2cceef$5e5c5076@applied-asynchrony.com' \
--to=holger@applied-asynchrony.com \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).