public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Cong Wang <xiyou.wangcong@gmail.com>
To: netdev@vger.kernel.org
Subject: Re: kernel BUG at net/core/skbuff.c:2839 RIP  [<ffffffff819109a2>] skb_segment+0x6b2/0x6d0
Date: Sun, 17 Nov 2013 19:59:56 +0000 (UTC)	[thread overview]
Message-ID: <slrnl8i828.8ar.xiyou.wangcong@linux-6brj.site> (raw)
In-Reply-To: 1287049824.20131117201744@eikelenboom.it

On Sun, 17 Nov 2013 at 19:17 GMT, Sander Eikelenboom <linux@eikelenboom.it> wrote:
> Hi Eric,
>
> With the linux-net changes from this merge window i get the kernel panic below (not with 3.12.0).
>
> It's on a machine running Xen, 2x rtl8169 nic, and using a bridge for guest networking.
> This panic in the host kernel only seems to occur when generating a lot of network traffic to and from a guest.
>
> I tried reverting "tcp: gso: fix truesize tracking" 0d08c42cf9a71530fef5ebcfe368f38f2dd0476f, but that didn't help.
>
> --
> Sander
>
> [ 1164.511712] ------------[ cut here ]------------
> [ 1164.518446] kernel BUG at net/core/skbuff.c:2839!

This is discussed in another long thread:
http://marc.info/?t=138419721200049&r=1&w=2

  reply	other threads:[~2013-11-17 20:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-17 19:17 kernel BUG at net/core/skbuff.c:2839 RIP [<ffffffff819109a2>] skb_segment+0x6b2/0x6d0 Sander Eikelenboom
2013-11-17 19:59 ` Cong Wang [this message]
2013-11-21 12:00 ` Sander Eikelenboom
2013-11-21 14:10   ` Eric Dumazet
2013-11-21 14:14     ` Sander Eikelenboom
2013-11-21 15:46     ` Sander Eikelenboom
2013-11-21 18:17     ` David Miller
2013-11-21 18:23       ` Eric Dumazet
2013-11-21 18:38         ` David Miller
2013-11-21 19:10           ` [PATCH v2] gso: handle new frag_list of frags GRO packets Eric Dumazet
2013-11-21 19:12             ` 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=slrnl8i828.8ar.xiyou.wangcong@linux-6brj.site \
    --to=xiyou.wangcong@gmail.com \
    --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