From: Konstantin Kuzov <master.nosferatu@gmail.com>
To: Steffen Klassert <steffen.klassert@secunet.com>
Cc: netdev@vger.kernel.org
Subject: Re: BUG: MARK in OUTPUT + ip_tunnel causes kernel panic
Date: Thu, 26 Sep 2013 06:06:04 +0400 [thread overview]
Message-ID: <20130926060604.4838802c@gmail.com> (raw)
In-Reply-To: <20130925085947.GY7660@secunet.com>
On Wed, 25 Sep 2013 10:59:47 +0200
Steffen Klassert wrote:
> > > When trying to tunnel traffic originating from the same machine as the
> > > tunnel endpoint, I am experiencing kernel panics for some types of
> > > traffic (ICMP and UDP). TCP seems not to be affected by this, at least
> > > I have not been able to trigger the panic.
> > >
> > > I have one tunnel (without an IP address) and use policy routing to
> > > steer some traffic through the tunnels.
> > [...]
> > > An interesting thing is that I have seen different kernel panics being
> > > triggered. The other one I have seen has RIP pointing to
> > > e1000_xmit_frame() and the message "protocol 0800 is buggy". However,
> > > the one I have posted is by far the most common.
> > I'm experiencing the same issue on two different machines. It happens on any
> > kernel starting from 3.10 when ip_tunnel/ip_tunnel_core were introduced.
> >
> Can you please try the patch below?
> I've posted the same patch already to netdev in the morning.
>
> Subject: [PATCH net 1/2] ip_tunnel: Fix a memory corruption in ip_tunnel_xmit
Thank you very much. All works fine with that patch applied.
next prev parent reply other threads:[~2013-09-26 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 14:00 BUG: MARK in OUTPUT + ip_tunnel causes kernel panic Kristian Evensen
2013-09-25 8:31 ` Konstantin Kuzov
2013-09-25 8:59 ` Steffen Klassert
2013-09-26 2:06 ` Konstantin Kuzov [this message]
2013-09-26 18:27 ` Kristian Evensen
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=20130926060604.4838802c@gmail.com \
--to=master.nosferatu@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;
as well as URLs for NNTP newsgroup(s).