From: Harald Welte <laforge@netfilter.org>
To: Andries Brouwer <Andries.Brouwer@cwi.nl>
Cc: Patrick McHardy <kaber@trash.net>,
akpm@osdl.org, torvalds@osdl.org, coreteam@netfilter.org,
linux-kernel@vger.kernel.org,
Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: [netfilter-core] [PATCH] no __initdata in netfilter?
Date: Tue, 14 Dec 2004 19:51:45 +0100 [thread overview]
Message-ID: <20041214185145.GE22577@sunbeam.de.gnumonks.org> (raw)
In-Reply-To: <20041214183911.GA15606@apps.cwi.nl>
[-- Attachment #1: Type: text/plain, Size: 2276 bytes --]
On Tue, Dec 14, 2004 at 07:39:11PM +0100, Andries Brouwer wrote:
> > If we _know_ that it works, and there is no bug, we could just add a
> > comment "This is handled correctly, since the ip_tables core copies the
> > data just as rulesets comming from userspace."
>
> I think that argument is valid only when satisfying the static tool
> is especially cumbersome or inefficient, requires ugly code, etc.
> In most cases a trivial rewrite will suffice, and the result is cleaner
> code, easier to maintain, fewer bugs.
yes, and that rewrite is what I did with the patch. Not really trivial,
but a small change.
Also, you only removed __initdata from ip_tables, but not arp_tables and
ip6_tables (which should have hit the same trigger in the tool)
> You say "but today nothing is wrong". But the longer the reasoning is,
> the easier one of the steps in the argument will be broken by some
> trivial change. By someone who did not know about all the invariants
> required by a certain piece of code.
Yes, but we're not talking about VM or filesystems, but a specific
function used by ip_tables internally.
I understand your point, though I think this is one of the cases where
your arguments apply the least. OTOTH, the __initdata structures we're
talking about are fairly big, space that you probably won't waste on
your embedded dsl router/firewall.
> > or alternatively pick up the (incremental) change attached to this mail.
> > I hope this makes your checker not spit any warnings.
>
> I checked, and indeed, no warnings for this patch.
great.
> But that is the only thing I checked. I would never submit it.
I checked that it compiles ;) The changes are fairly trivial.
> Probably you should send it to davem and see whether he likes it.
We'll include it with the next patchset that goes to davem for mainline
inclusion.
> Andries
--
- Harald Welte <laforge@netfilter.org> http://www.netfilter.org/
============================================================================
"Fragmentation is like classful addressing -- an interesting early
architectural error that shows how much experimentation was going
on while IP was being designed." -- Paul Vixie
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-12-14 18:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-14 1:37 Andries Brouwer
2004-11-14 7:56 ` [netfilter-core] " Patrick McHardy
2004-11-14 11:26 ` Andries Brouwer
2004-12-14 13:00 ` Harald Welte
2004-12-14 15:52 ` Linus Torvalds
2004-12-14 18:39 ` Andries Brouwer
2004-12-14 18:51 ` Harald Welte [this message]
2004-12-15 4:21 ` Rusty Russell
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=20041214185145.GE22577@sunbeam.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=Andries.Brouwer@cwi.nl \
--cc=akpm@osdl.org \
--cc=coreteam@netfilter.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=torvalds@osdl.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 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®