From: Willy Tarreau <willy@w.ods.org>
To: Roberto Nibali <ratz@drugphish.ch>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.4] TCP window tracking: nf-log
Date: Sun, 4 Dec 2005 19:12:36 +0100 [thread overview]
Message-ID: <20051204181236.GA6314@alpha.home.local> (raw)
In-Reply-To: <4393304C.2030100@drugphish.ch>
Hi Roberto,
On Sun, Dec 04, 2005 at 07:07:08PM +0100, Roberto Nibali wrote:
> Hi Willy,
>
> Thanks for your review.
>
> > On Mon, Nov 21, 2005 at 11:15:34AM +0100, Roberto Nibali wrote:
> >> Hello,
> >>
> >> This is the rediffed nf-log patch against 2.4.32, which is needed in
> >> order to have the core tcp window tracking patch working in 2.4.x kernels.
> >
> > I've fixed two things which prevented it from compiling :
> > - removed a space change in ip_vs_conn.c which might have been caused
> > by a change in your reference 2.4.32 tree ;
>
> Hmm, I hopefully haven't included IPVS stuff into the nf-log patch, have
> I? I don't seem to be able to find this change in your proposal.
Here is the chunk I found in your patch and which I removed :
diff -Nur linux-2.4.32-orig/net/ipv4/ipvs/ip_vs_conn.c linux-2.4.32-pab2/net/ipv4/ipvs/ip_vs_conn.c
--- linux-2.4.32-orig/net/ipv4/ipvs/ip_vs_conn.c 2005-10-27 17:17:13 +0200
+++ linux-2.4.32-pab2/net/ipv4/ipvs/ip_vs_conn.c 2005-10-27 17:17:54 +0200
@@ -246,7 +246,7 @@
struct ip_vs_conn *ip_vs_ct_in_get
(int protocol, __u32 s_addr, __u16 s_port, __u32 d_addr, __u16 d_port)
{
- unsigned hash:
+ unsigned hash;
struct ip_vs_conn *cp;
hash = ip_vs_conn_hashkey(protocol, s_addr, s_port);
Just white spaces, but it was rejected. That's why I believe that your
reference tree has been touched.
> > - ip6t_log_target() was not properly renamed as ip6t_log_packet(), so
> > build was broken with IPv6 enabled.
>
> I'll see to it, thanks. As you found out, I've never compiled my patches
> with IPv6 selected; thanks for checking it.
>
> > Please use the attached one as an update.
>
> I will, once I get some time again to work on the kernel.
>
> > I'm still in the process of building a new kernel with all this, I'll keep
> > you informed.
>
> Excellent.
Nearly ready to boot it :-)
> Have a nice evening,
> Roberto Nibali, ratz
Cheers,
Willy
next prev parent reply other threads:[~2005-12-04 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 10:15 [PATCH 2.4] TCP window tracking: nf-log Roberto Nibali
2005-12-04 13:51 ` Willy Tarreau
2005-12-04 18:07 ` Roberto Nibali
2005-12-04 18:12 ` Willy Tarreau [this message]
2005-12-04 19:38 ` Roberto Nibali
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=20051204181236.GA6314@alpha.home.local \
--to=willy@w.ods.org \
--cc=netfilter-devel@lists.netfilter.org \
--cc=ratz@drugphish.ch \
/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.