From: Rusty Russell <rusty@rustcorp.com.au>
To: Rik van Riel <riel@surriel.com>
Cc: linux-kernel@vger.kernel.org,
"David S. Miller" <davem@redhat.com>,
coreteam@netfilter.org
Subject: Re: [netfilter-core] [PATCH] compile fix ipfw
Date: Thu, 17 Apr 2003 15:16:58 +1000 [thread overview]
Message-ID: <20030417060556.75AA12C019@lists.samba.org> (raw)
In-Reply-To: Your message of "Wed, 16 Apr 2003 21:11:31 -0400." <Pine.LNX.4.44.0304162109530.12650-100000@chimarrao.boston.redhat.com>
In message <Pine.LNX.4.44.0304162109530.12650-100000@chimarrao.boston.redhat.co
m> you write:
>
> In the patch that went to marcelo a few days ago the reset
> argument to ip_chain_procinfo() got removed, but there's still
> a code block inside the function that references that variable.
>
> This patch gets rid of that (presumably old) code block. Note
> that I didn't cc this to Marcelo because I'm not 100% sure, so
> please check it.
This looks fine to me: there used to be magic in 2.0 which meant when
you opened the proc file for writing as well as reading, it'd reset
the counters.
These days, the infrastructure doesn't support such a hack.
Please fwd to Marcelo.
Thanks!
Rusty.
> @@ -1176,12 +1176,6 @@ static int ip_chain_procinfo(int stage,
> len = last_len;
> break;
> }
> - else if(reset)
> - {
> - /* This needs to be done at this specific place! */
> - i->fw_pcnt=0L;
> - i->fw_bcnt=0L;
> - }
> last_len = len;
> i=i->fw_next;
> }
>
--
Anyone who quotes me in their sig is an idiot. -- Rusty Russell.
next prev parent reply other threads:[~2003-04-17 5:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-17 1:11 Rik van Riel
2003-04-17 1:13 ` David S. Miller
2003-04-17 5:16 ` Rusty Russell [this message]
2003-04-18 8:39 ` [netfilter-core] " David S. Miller
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=20030417060556.75AA12C019@lists.samba.org \
--to=rusty@rustcorp.com.au \
--cc=coreteam@netfilter.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@surriel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®