Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: Felipe W Damasio <felipewd@gmail.com>
Cc: Avi Kivity <avi@redhat.com>, David Miller <davem@davemloft.net>,
	Patrick McHardy <kaber@trash.net>,
	linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets
Date: Tue, 13 Jul 2010 17:49:53 +0200	[thread overview]
Message-ID: <1279036193.2634.468.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTilrIByt4xAHhsBsKo3nDfv0_c3sF-dCiTiYiPnu@mail.gmail.com>

Le mardi 13 juillet 2010 à 11:49 -0300, Felipe W Damasio a écrit :
> Hi Mr. Dumazet,
> 
> 2010/7/13 Eric Dumazet <eric.dumazet@gmail.com>:
> > I currently have no fresh ideas. If you want this problem to be solved,
> > its important to setup in your lab a workload to trigger again and again
> > the bug, in order to provide us more crash information.
> 
>  Right. I've been running non-stop since the first bug happened, but
> so far the problem hasn't surfaced again :-(
> 
>  I've been using the kernel with the patch that you provided me
> (nf_tproxy.c). Is there a chance that patch fixed the problem?

This is a real bug, but I dont think it can fix your problem.

Looking again at your crash, we see RCX=0x720, decimal 1824

As its skb->len, we are freeing an skb that was collapsed or something
like that, since 1824 > 1460 (the normal MSS on ethernet)

GRO is off on your machine.

But coincidently 0x0720 is also a blank char for VGA screen...
(0x20 : ASCII space, 0x07 : default attribute)

So maybe you hit a corruption outside of network stack.

  reply	other threads:[~2010-07-13 15:49 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTimn8A0cYZmwNZYitRkBHKKFe4HQ5GU626DLugkk@mail.gmail.com>
2010-07-08 22:06 ` Squid hang up on 2.6.34 Eric Dumazet
     [not found] ` <AANLkTil49m6Ul2bauiH4Pwn-6ykrYTFmSO6_SxqQgD_e@mail.gmail.com>
2010-07-08 22:08   ` Eric Dumazet
2010-07-09 15:03     ` Felipe W Damasio
2010-07-09 16:03       ` Felipe W Damasio
2010-07-09 17:13       ` [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets Eric Dumazet
2010-07-09 17:53         ` David Miller
2010-07-09 18:16         ` Felipe W Damasio
2010-07-10  3:18         ` Felipe W Damasio
2010-07-10  6:17           ` Eric Dumazet
2010-07-10 19:30             ` David Miller
2010-07-11  3:11               ` Felipe W Damasio
2010-07-11  7:11                 ` Felipe W Damasio
2010-07-11  7:13                   ` Felipe W Damasio
2010-07-11  8:36               ` Eric Dumazet
2010-07-11  5:19             ` Avi Kivity
2010-07-11  8:02               ` Eric Dumazet
2010-07-12  0:52                 ` Felipe W Damasio
2010-07-12 18:49                   ` Felipe W Damasio
2010-07-13 14:24                     ` Felipe W Damasio
2010-07-13 14:40                       ` Eric Dumazet
2010-07-13 14:49                         ` Felipe W Damasio
2010-07-13 15:49                           ` Eric Dumazet [this message]
2010-07-13 20:55                             ` Felipe W Damasio
2010-07-13 21:06                               ` Felipe W Damasio
2010-07-14  3:21                               ` Eric Dumazet
2010-07-14  3:27                                 ` Felipe W Damasio
2010-07-14  3:43                                   ` Eric Dumazet
2010-07-14  3:51                                     ` Felipe W Damasio
2010-07-14  6:56                                       ` Bill Fink
2010-07-16 15:41                                   ` Felipe W Damasio
2010-07-16 15:52                                     ` Eric Dumazet
2010-07-14 11:41         ` Patrick McHardy

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=1279036193.2634.468.camel@edumazet-laptop \
    --to=eric.dumazet@gmail.com \
    --cc=avi@redhat.com \
    --cc=davem@davemloft.net \
    --cc=felipewd@gmail.com \
    --cc=kaber@trash.net \
    --cc=linux-kernel@vger.kernel.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