From: Wolfgang Walter <linux@stwm.de>
To: netdev@vger.kernel.org
Cc: Wei Wang <weiwan@google.com>
Subject: kernels >= v4.12 oops/crash with ipsec-traffic: partly bisected
Date: Thu, 30 Aug 2018 12:48:25 +0200 [thread overview]
Message-ID: <3482600.6PjfSIYROA@stwm.de> (raw)
Hello,
kernels >= 4.12 do not work on one of our main routers. They crash as soon as
ipsec-tunnels are configured and ipsec-traffic actually flows.
Just configuring ipsec (that is starting strongswan) does not trigger the
oops.
I finally found time to bisect that. Though I have not completed that yet, I
already narrowed it down to the following commits
good: d24406c85d123df773bc4df88ad5da2233896919
udp: call dst_hold_safe() in udp_sk_rx_set_dst()
bad: 5b7c9a8ff828287af5aebe93e707271bf1a82cc3
net: remove dst gc related code
Commits in between are almost all changes to remove dst gc.
Now we have other machines which run just fine with the very same kernels
doing ipsec. They differ insofar as they have much less cores, do not use the
ixgbe driver, do not have 10G and terminate only a few tunnels instead of
hundreds.
I already tested distribution kernels > 4.12 from debian, they also crash.
Regards,
--
Wolfgang Walter
Studentenwerk München
Anstalt des öffentlichen Rechts
next reply other threads:[~2018-08-30 14:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 10:48 Wolfgang Walter [this message]
2018-08-30 18:53 ` kernels > v4.12 oops/crash with ipsec-traffic: bisected to b838d5e1c5b6e57b10ec8af2268824041e3ea911: ipv4: mark DST_NOGC and remove the operation of dst_free() Wolfgang Walter
2018-08-31 6:50 ` Steffen Klassert
2018-09-07 9:53 ` Wolfgang Walter
2018-09-07 20:22 ` Wolfgang Walter
2018-09-07 21:10 ` Wolfgang Walter
2018-09-10 6:37 ` Steffen Klassert
2018-09-10 8:18 ` Kristian Evensen
2018-09-10 10:46 ` Wolfgang Walter
2018-09-11 10:33 ` Steffen Klassert
2018-09-11 16:53 ` Wolfgang Walter
2018-09-11 19:02 ` Tobias Hommel
2018-09-12 8:50 ` Steffen Klassert
2018-09-12 15:18 ` Tobias Hommel
2018-09-19 18:38 ` Tobias Hommel
2018-09-10 9:06 ` Tobias Hommel
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=3482600.6PjfSIYROA@stwm.de \
--to=linux@stwm.de \
--cc=netdev@vger.kernel.org \
--cc=weiwan@google.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;
as well as URLs for NNTP newsgroup(s).