From: Roberto Nibali <ratz@drugphish.ch>
To: Willy Tarreau <willy@w.ods.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.4] TCP window tracking: nf-log
Date: Sun, 04 Dec 2005 20:38:32 +0100 [thread overview]
Message-ID: <439345B8.7000504@drugphish.ch> (raw)
In-Reply-To: <20051204181236.GA6314@alpha.home.local>
>>> 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.
Well, this is more than a whitespace fix, I must have put a colon at
this place while working on my IPVS extension on one drop and later when
compile testing I replaced the erroneous colon with a semicolon. However
I didn't read my patch before sending to netfilter. My bad, thanks for
updating it, Willy. Next time I will proof-read my patches for such
stupid mistakes.
> Nearly ready to boot it :-)
Good luck, if you need kdb patches, I have them ready :).
http://www.drugphish.ch/patches/ratz/kernel/2.4.x/linux-2.4.32-kdb-v4.3-common-1.diff
http://www.drugphish.ch/patches/ratz/kernel/2.4.x/linux-2.4.32-kdb-v4.3-i386-1.diff
Cheers,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
prev parent reply other threads:[~2005-12-04 19:38 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
2005-12-04 19:38 ` Roberto Nibali [this message]
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=439345B8.7000504@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=netfilter-devel@lists.netfilter.org \
--cc=willy@w.ods.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.