From: Phil Oester <kernel@linuxace.com>
To: Patrick McHardy <kaber@trash.net>
Cc: netfilter-devel@lists.netfilter.org,
Phil Oester <netfilter@linuxace.com>
Subject: Re: [PATCH] kernel panic with rpc.patch
Date: Thu, 2 Sep 2004 21:21:13 -0700 [thread overview]
Message-ID: <20040903042113.GA19923@linuxace.com> (raw)
In-Reply-To: <4137CE4D.7070702@trash.net>
[-- Attachment #1: Type: text/plain, Size: 794 bytes --]
On Fri, Sep 03, 2004 at 03:52:13AM +0200, Patrick McHardy wrote:
> Phil Oester wrote:
>
> >Some useless __MOD_INC_USE_COUNT macros make rpc patch panic on boot.
> >The below removes them. Boot tested.
>
> Applied, but wondering on second thought. There are still two
> __MOD_DEC_USE_COUNT left, and __MOD_INC_USE_COUNT does actually
> do something :) Why are they useless ?
Yes, perhaps 'useless' is the wrong word -- they do something, but
something which is deprecated and in 2.6 netfilter nonexistent. And
following davem's policy of no refcounts for network drivers [1], it
seems to make sense.
Agreed, however, that removing the INC without also removing the DEC
is sloppy. Attached find a patch to do so.
Phil
[1] http://www.uwsg.iu.edu/hypermail/linux/kernel/0307.3/0403.html
[-- Attachment #2: patch-rpc2 --]
[-- Type: text/plain, Size: 514 bytes --]
diff -ru pom-orig/rpc/linux/net/ipv4/netfilter/ipt_rpc.c pom-new/rpc/linux/net/ipv4/netfilter/ipt_rpc.c
--- pom-orig/rpc/linux/net/ipv4/netfilter/ipt_rpc.c 2004-09-03 00:17:53.859176224 -0400
+++ pom-new/rpc/linux/net/ipv4/netfilter/ipt_rpc.c 2004-09-03 00:17:41.524051448 -0400
@@ -412,10 +412,6 @@
{
DEBUGP("unregistering match\n");
ipt_unregister_match(&rpc_match);
-
- DEBUGP("decrementing usage counts\n");
- __MOD_DEC_USE_COUNT(ip_conntrack_rpc_tcp);
- __MOD_DEC_USE_COUNT(ip_conntrack_rpc_udp);
}
next prev parent reply other threads:[~2004-09-03 4:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 23:23 [PATCH] kernel panic with rpc.patch Phil Oester
2004-09-03 1:52 ` Patrick McHardy
2004-09-03 4:21 ` Phil Oester [this message]
2004-09-03 16:15 ` 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=20040903042113.GA19923@linuxace.com \
--to=kernel@linuxace.com \
--cc=kaber@trash.net \
--cc=netfilter-devel@lists.netfilter.org \
--cc=netfilter@linuxace.com \
/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.