From: Kevin Locke <kevin@kevinlocke.name>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org
Subject: Re: Bisected 4.14 Regression: IPsec transport mode breakage
Date: Fri, 17 Nov 2017 10:46:43 -0700 [thread overview]
Message-ID: <20171117174643.z3k6uzgrdnkdh6if@kevinolos> (raw)
In-Reply-To: <20171117100346.32zc6mv7bc2faamx@gauss3.secunet.de>
On Fri, 2017-11-17 at 11:03 +0100, Steffen Klassert wrote:
> On Wed, Nov 15, 2017 at 09:46:19AM -0700, Kevin Locke wrote:
>> I have bisected the issue to commit c9f3f813d462. I have attached the
>> client ipsec.conf as well as the syslog during the connection attempt
>> for both c9f3f813d462 (bad) and cf3796675174 (good).
>
> The offending commit is already reverted in the 'net' tree
> and will be available in mainline soon.
Great, thank you! I tested davem/net#94802151894d and can confirm
that it works and fixes the issue for me. Thanks again.
--
Cheers, | kevin@kevinlocke.name | XMPP: kevin@kevinlocke.name
Kevin | https://kevinlocke.name | IRC: kevinoid on freenode
prev parent reply other threads:[~2017-11-17 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-15 16:46 Bisected 4.14 Regression: IPsec transport mode breakage Kevin Locke
2017-11-17 10:03 ` Steffen Klassert
2017-11-17 17:46 ` Kevin Locke [this message]
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=20171117174643.z3k6uzgrdnkdh6if@kevinolos \
--to=kevin@kevinlocke.name \
--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