From: Patrick McHardy <kaber@trash.net>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: David Wu <davidwu@arcturusnetworks.com>,
Netfilter Developer Mailing List
<netfilter-devel@vger.kernel.org>
Subject: Re: iptables (1.4.2 release) failed to run on embedded system with "can't initialize iptables table `filter'"
Date: Wed, 26 Nov 2008 17:25:13 +0100 [thread overview]
Message-ID: <492D7869.6090808@trash.net> (raw)
In-Reply-To: <alpine.LNX.1.10.0811261711080.2741@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> (Patrick, try not to screw up utf-8 in the git log too often ;-)
If you try not to use it at every possible opportunity ... :)
> commit 3430170eca6bf73b590ddbd1a1ee0573862ff555
> Author: Jan Engelhardt <jengelh@medozas.de>
> Date: Wed Nov 26 17:13:57 2008 +0100
>
> libiptc: guard chain index allocation for different malloc implementations
>
> Some libc implementations such as µClibc return NULL on malloc(0).
> They are free to do that per C standard.
Applied, thanks.
That behaviour is a bit stupid in my opinion though, it puts the burden
on every caller using dynamically calculated sizes. I would expect more
things to break from this.
--
To unsubscribe from this list: send the line "unsubscribe netfilter-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-11-26 16:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-21 14:51 iptables (1.4.2 release) failed to run on embedded system with "can't initialize iptables table `filter'" David Wu
2008-11-21 16:07 ` Jan Engelhardt
2008-11-21 18:35 ` David Wu
2008-11-22 11:06 ` Jan Engelhardt
2008-11-25 17:10 ` David Wu
2008-11-25 17:45 ` Jan Engelhardt
2008-11-25 19:07 ` David Wu
2008-11-26 16:15 ` Jan Engelhardt
2008-11-26 16:25 ` Patrick McHardy [this message]
2008-11-26 17:14 ` Jan Engelhardt
-- strict thread matches above, loose matches on Subject: below --
2008-11-19 21:51 David Wu
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=492D7869.6090808@trash.net \
--to=kaber@trash.net \
--cc=davidwu@arcturusnetworks.com \
--cc=jengelh@medozas.de \
--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 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.