From: netfilter@interlinx.bc.ca
To: Netfilter Development Mailinglist <netfilter-devel@lists.netfilter.org>
Subject: tcp-window-tracking vs. pending/24_conntrack-nosysctl.patch
Date: Wed, 2 Apr 2003 21:51:51 -0500 [thread overview]
Message-ID: <20030403025151.GA1702@pc.ilinx> (raw)
[-- Attachment #1: Type: text/plain, Size: 895 bytes --]
There is a patch in pending that makes the tcp-window-tracking patch
fail to apply cleanly. The patch in
pending/24_conntrack-nosysctl.patch:
--- linux-2.4.21-pre5-ac3/net/ipv4/netfilter/ip_conntrack_core.c Sat Mar 15 12:16:55 2003
+++ linux-2.4.21-pre5-ac3-fixed/net/ipv4/netfilter/ip_conntrack_core.c Sat Mar 15 12:23:34 2003
@@ -1478,8 +1478,10 @@
ip_ct_attach = ip_conntrack_attach;
return ret;
+#ifdef CONFIG_SYSCTL
err_free_ct_cachep:
kmem_cache_destroy(ip_conntrack_cachep);
+#endif /*CONFIG_SYSCTL*/
err_free_hash:
vfree(ip_conntrack_hash);
err_unreg_sockopt:
is not accounted for in hunk 5 to file
net/ipv4/netfilter/ip_conntrack_core.c in
extra/tcp-window-tracking.patch.
I guess the question is, should it be expected that patches in suites
like extra should apply if all of submitted and pending are applied.
b.
--
Brian J. Murrell
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2003-04-03 2:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 2:51 netfilter [this message]
2003-04-03 10:15 ` tcp-window-tracking vs. pending/24_conntrack-nosysctl.patch Martin Josefsson
2003-04-03 11:15 ` Hervé Eychenne
2003-04-03 11:21 ` Martin Josefsson
2003-04-04 8:46 ` Jozsef Kadlecsik
2003-04-05 11:16 ` Martin Josefsson
2003-04-05 12:28 ` Martin Josefsson
2003-04-05 14:47 ` Martin Josefsson
2003-04-05 14:51 ` Jozsef Kadlecsik
2003-04-05 15:18 ` Martin Josefsson
2003-04-05 14:45 ` Jozsef Kadlecsik
2003-04-03 13:57 ` netfilter
2003-04-03 17:23 ` rmmod ip_conntrack hangs ...? marian stagarescu
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=20030403025151.GA1702@pc.ilinx \
--to=netfilter@interlinx.bc.ca \
--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.