From: Steffen Klassert <steffen.klassert@secunet.com>
To: Nick Huber <nick.huber@multapplied.net>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: skb_over_panic when sending esp traffic from a vmware guest
Date: Tue, 22 Aug 2017 07:32:49 +0200 [thread overview]
Message-ID: <20170822053249.GK31224@secunet.com> (raw)
In-Reply-To: <CY1PR17MB0552F3C75C45DBC72799A0F187830@CY1PR17MB0552.namprd17.prod.outlook.com>
On Thu, Aug 17, 2017 at 07:19:03PM +0000, Nick Huber wrote:
> I've been experience the following traceback since upgrading from the 4.9 kernel to the 4.11 branch. I've only seen this in a few VMWare guests and I haven't been able to narrow down what exactly is causing it. I'm not familiar with kernel debugging but any help in tracing this down would be appreciated.
Can you give some details about your setup?
>From the backtrace I see that you use GRE tunnels.
How is the setup of the GRE tunnel and the SAs?
How is routing done? In particular I'm interested
if you use routing by netfilter or socket marks.
prev parent reply other threads:[~2017-08-22 5:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-17 19:19 skb_over_panic when sending esp traffic from a vmware guest Nick Huber
2017-08-22 5:32 ` Steffen Klassert [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=20170822053249.GK31224@secunet.com \
--to=steffen.klassert@secunet.com \
--cc=netdev@vger.kernel.org \
--cc=nick.huber@multapplied.net \
/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