From: Andrew Morton <akpm@linux-foundation.org>
To: netdev@vger.kernel.org, Jeremy Fitzhardinge <jeremy@goop.org>,
Chris Wright <chrisw@sous-sol.org>
Cc: bugzilla-daemon@bugzilla.kernel.org,
bugme-daemon@bugzilla.kernel.org,
James Chapman <jchapman@katalix.com>,
heil@terminal-consulting.de
Subject: Re: [Bugme-new] [Bug 16529] New: xennet driver crashes when using with pseudowire aka l2tpv3
Date: Wed, 25 Aug 2010 15:31:07 -0700 [thread overview]
Message-ID: <20100825153107.2f547f0e.akpm@linux-foundation.org> (raw)
In-Reply-To: <bug-16529-10286@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Fri, 6 Aug 2010 12:46:18 GMT
bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=16529
>
> Summary: xennet driver crashes when using with pseudowire aka
> l2tpv3
> Product: Networking
> Version: 2.5
> Kernel Version: 2.6.35
> Platform: All
> OS/Version: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Other
> AssignedTo: acme@ghostprotocols.net
> ReportedBy: heil@terminal-consulting.de
> Regression: No
>
>
> I tried to use use the new l2tpv3 implementation on two xen domU's but one of
> them is crashing when the first l2tpv3 packet is received.
>
> As a great man mentioned:
> --
> guessing that eth_type_trans() has tried to pull an ethernet header from
> the skb and has run off the end, which suggests an issue with the skb
> that was passed up. Does the ethernet driver do proper alignment of data
> in its skbs? Perhaps it doesn't allocate as much headroom as other
> drivers? Perhaps the L2TP code assumes things about the skb that aren't
> valid..
> --
> Here is a link for the setup
> http://www.pastebin.org/445975
> and here a link with more details about the crash http://pastebin.org/449221
>
> According the the hints from James Chapmann we tried generic x86 with a
> different nic driver like e1000 and this works without any problem.
>
> Iam using OpenWrt to create the system images. To speed up the process i would
> prepare Xen images, make them available or whatever is wished because
> pseudowire is already ready in OpenWrt Trunk so that every man also with "price
> sensitivy" hardware can use it.
>
Seems to be a problem with xennet afacit?
next parent reply other threads:[~2010-08-25 22:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-16529-10286@https.bugzilla.kernel.org/>
2010-08-25 22:31 ` Andrew Morton [this message]
2010-08-25 22:56 ` [Bugme-new] [Bug 16529] New: xennet driver crashes when using with pseudowire aka l2tpv3 Jeremy Fitzhardinge
2010-08-26 7:10 ` Ian Campbell
2010-08-26 7:22 ` Eric Dumazet
2010-08-26 8:03 ` Eric Dumazet
2010-08-26 8:14 ` Ian Campbell
2010-08-26 8:34 ` Eric Dumazet
2010-08-26 8:55 ` Ian Campbell
2010-08-26 9:44 ` Eric Dumazet
2010-08-26 20:30 ` David Miller
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=20100825153107.2f547f0e.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=chrisw@sous-sol.org \
--cc=heil@terminal-consulting.de \
--cc=jchapman@katalix.com \
--cc=jeremy@goop.org \
--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).