From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>,
Mark Ryden <markryde@gmail.com>
Subject: Re: netfilter module and shared libraries
Date: Thu, 01 Apr 2010 14:05:22 +0200 [thread overview]
Message-ID: <4BB48C02.40601@trash.net> (raw)
In-Reply-To: <alpine.LSU.2.01.1004011358350.17429@obet.zrqbmnf.qr>
Jan Engelhardt wrote:
> On Thursday 2010-04-01 13:46, Mark Ryden wrote:
>
>> Is there a way to avoid this when adding such a rule,
>> using some default mechansim ?
>
> Let's ask Patrick:
>
> What do you think of enabling iptables to assume targets with .size=0
> (which don't have options by design) if there was no libxt_XYZ.so found?
> That would make things like libxt_NOTRACK.c obsolete, too.
No general objections, but how many modules are there really
that don't take options? Feel free to try, if your patch doesn't
affect error reporting and stays below 15 lines, I'll apply
it :)
prev parent reply other threads:[~2010-04-01 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 11:46 netfilter module and shared libraries Mark Ryden
2010-04-01 12:01 ` Jan Engelhardt
2010-04-01 12:05 ` Patrick McHardy [this message]
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=4BB48C02.40601@trash.net \
--to=kaber@trash.net \
--cc=jengelh@medozas.de \
--cc=markryde@gmail.com \
--cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).