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: Wed, 14 Jul 2010 05:43:05 +0200 [thread overview]
Message-ID: <1279078985.2444.105.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTikkcaionMp3SJLgo3JmCjxQ7rPZv3-3_RbxCx_4@mail.gmail.com>
Le mercredi 14 juillet 2010 à 00:27 -0300, Felipe W Damasio a écrit :
> Hi Mr. Dumazet,
>
> 2010/7/14 Eric Dumazet <eric.dumazet@gmail.com>:
> > RDX being the sk pointer (and sk+0x38 contains the corrupted "sk_prot" value)
> > , we notice RBP contains same "sk" value + 0x200000 (2 Mbytes).
> >
> > (same remark on your initial bug report)
> >
> > Could you enable CONFIG_FRAME_POINTER=y in your config ?
>
> I can, but my bosses will kick my ass if I bring down the ISP again :)
>
I have no guarantee at all, even if we find the bug.
> If you think it's the only way to find the problem I'll tell them that
> I need to do it. In this case, please tell me what other config
> options/tools I can use to get as much info as possible...since I'll
> probably be able to test this only once more on the production
> environment for debugging purposes.
>
You really should try to setup a lab to trigger the bug, and not doing
experiments on production :)
next prev parent reply other threads:[~2010-07-14 3:43 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
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 [this message]
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=1279078985.2444.105.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