From: Patrick McHardy <kaber@trash.net>
To: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] Fix NAT issue in 2.6.30.4+
Date: Thu, 17 Sep 2009 13:24:39 +0200 [thread overview]
Message-ID: <4AB21C77.1010306@trash.net> (raw)
In-Reply-To: <alpine.DEB.2.00.0909171319040.5343@blackhole.kfki.hu>
Jozsef Kadlecsik wrote:
> On Thu, 17 Sep 2009, Patrick McHardy wrote:
>
>> I got one reject in the removal of nf_conntrack_tcp_update() due
>> to the use of write_lock() instead of spin_lock() in your patch
>> (seems to be based on an old tree), this is the patch I committed:
>
> Uhh, I forgot to forward-port the patch, sorry: I used the 2.6.30.5 tree
> for verifying the bug and testing the fix.
I double checked and it looks fine, apart from the minor reject.
I'll give it some testing myself before pushing upstream.
next prev parent reply other threads:[~2009-09-17 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-10 19:37 [PATCH] Fix NAT issue in 2.6.30.4+ Jozsef Kadlecsik
2009-09-17 10:51 ` Thomas Jarosch
2009-09-17 11:06 ` Patrick McHardy
2009-09-17 11:22 ` Jozsef Kadlecsik
2009-09-17 11:24 ` Patrick McHardy [this message]
2009-09-22 15:34 ` Thomas Jarosch
2009-10-22 10:55 ` Thomas Jarosch
2009-10-28 15:54 ` 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=4AB21C77.1010306@trash.net \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=netfilter-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.