From: Eric Dumazet <eric.dumazet@gmail.com>
To: Felipe W Damasio <felipewd@gmail.com>,
David Miller <davem@davemloft.net>,
Patrick McHardy <kaber@trash.net>
Cc: linux-kernel@vger.kernel.org, netdev <netdev@vger.kernel.org>
Subject: [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets
Date: Fri, 09 Jul 2010 19:13:00 +0200 [thread overview]
Message-ID: <1278695580.2696.55.camel@edumazet-laptop> (raw)
In-Reply-To: <AANLkTiliBClahTfb41M5BDi1etg5pgkqEz_VfGrn_mK4@mail.gmail.com>
Le vendredi 09 juillet 2010 à 12:03 -0300, Felipe W Damasio a écrit :
> Hi,
>
> 2010/7/8 Eric Dumazet <eric.dumazet@gmail.com>:
> > Please try to reproduce a new report.
> >
> > It looks like a memory corruption, and it would be good to see if a
> > common pattern is occurring.
>
> I'm trying..the thing is the freeze occured on the machine that sits
> on a 200Mbps ISP in bridge-mode. Since the machine frooze, and the
> whole ISP went down for a few minutes, I'm not allowed to run any
> tests on it.
>
> I've setup the same scenario on a lab, but since last night been
> unable to reproduce the bug. Maybe there's a clue on the this crash
> below that can help me write some program to trigger the problem?
>
Reviewing tproxy stuff I spotted a problem in nf_tproxy_assign_sock()
but I could not see how it could explain your crash.
We can read uninitialized memory and trigger a fault in
nf_tproxy_assign_sock(), not later in tcp_recvmsg()...
David, Patrick, what do you think ?
Thanks
[PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets
transparent field of a socket is either inet_twsk(sk)->tw_transparent
for timewait sockets, or inet_sk(sk)->transparent for other sockets
(TCP/UDP).
Signed-off-by: Eric Dumazet <eric.dumazet@gmail.com>
---
diff --git a/net/netfilter/nf_tproxy_core.c b/net/netfilter/nf_tproxy_core.c
index 5490fc3..daab8c4 100644
--- a/net/netfilter/nf_tproxy_core.c
+++ b/net/netfilter/nf_tproxy_core.c
@@ -70,7 +70,11 @@ nf_tproxy_destructor(struct sk_buff *skb)
int
nf_tproxy_assign_sock(struct sk_buff *skb, struct sock *sk)
{
- if (inet_sk(sk)->transparent) {
+ bool transparent = (sk->sk_state == TCP_TIME_WAIT) ?
+ inet_twsk(sk)->tw_transparent :
+ inet_sk(sk)->transparent;
+
+ if (transparent) {
skb_orphan(skb);
skb->sk = sk;
skb->destructor = nf_tproxy_destructor;
next prev parent reply other threads:[~2010-07-09 17:13 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 ` Eric Dumazet [this message]
2010-07-09 17:53 ` [PATCH] tproxy: nf_tproxy_assign_sock() can handle tw sockets 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
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=1278695580.2696.55.camel@edumazet-laptop \
--to=eric.dumazet@gmail.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