All of lore.kernel.org
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: Harald Welte <laforge@netfilter.org>
Cc: netfilter-devel@lists.netfilter.org
Subject: Re: [PATCH 2.6] NETFILTER: tcp window tracking
Date: Sat, 24 Jul 2004 23:22:39 -0700	[thread overview]
Message-ID: <20040724232239.29bd3ee3.davem@redhat.com> (raw)
In-Reply-To: <20040724153427.GV2848@obroa-skai.de.gnumonks.org>

On Sat, 24 Jul 2004 11:34:27 -0400
Harald Welte <laforge@netfilter.org> wrote:

> This is the tcp window tracking patch, incremental to all previous
> changes.  It is now by default enabled (i.e. in 'conservative' mode).
> If you think it's better to leave it disabled ('liberal' mode), you can
> change ip_conntrack_tcp_be_liberal to a different default value.

All 12 incremental patches applied, plus this window
tracking code.

Three comments:

1) Patch 7, the seq_file patch was slightly busted,
   look at this hunk:

 #ifdef CONFIG_IP_NF_CT_ACCT
 static unsigned int
-print_counters(char *buffer, struct ip_conntrack_counter *counter)
+seq_print_counters(struct seq_file *s, struct ip_conntrack_counter *counter)
 {
-	return sprintf(buffer, "packets=%llu bytes=%llu ", 
-			counter->packets, counter->bytes);
+	return seq_printf(s, "packets=%llu bytes=%llu ",
+			  counter->packets, counter->bytes);
 }
 #else
 #define seq_print_counters(x, y)	0
 #endif
 
   Hehe, last #define line should be something like:

-#define print_counters(x, y)	0
+#define seq_print_counters(x, y)	0

   I fixed that up by hand.

2) ipt_sctp match had double slashes in the path names in
   the diff, that confuses diffstat and thus my automated
   scripts.

3) Yes, I think the new window tracking code mode should
   be on by default.

Thanks a lot Harald.

  reply	other threads:[~2004-07-25  6:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-24 15:34 [PATCH 2.6] NETFILTER: tcp window tracking Harald Welte
2004-07-25  6:22 ` David S. Miller [this message]
2004-07-25 13:12   ` Harald Welte
2004-07-25 18:02     ` David S. Miller
2004-07-25 20:05       ` Harald Welte

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=20040724232239.29bd3ee3.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=laforge@netfilter.org \
    --cc=netfilter-devel@lists.netfilter.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.