From: Fabian Hugelshofer <hugelshofer2006@gmx.ch>
To: Pablo Neira Ayuso <pablo@netfilter.org>
Cc: Patrick McHardy <kaber@trash.net>, netfilter-devel@vger.kernel.org
Subject: Re: [PATCH 1/3] libnfnetlink byte alignment
Date: Thu, 05 Jun 2008 13:55:10 +0100 [thread overview]
Message-ID: <4847E22E.8010701@gmx.ch> (raw)
In-Reply-To: <48470C52.1080306@netfilter.org>
Pablo Neira Ayuso wrote:
>> Patrick McHardy wrote:
>>> Fabian Hugelshofer wrote:
>>>> Aligns buffers to maximum alignment of architecture to make the cast of
>>>> char pointers to struct pointers more portable.
>>>>
>>>> Signed-off-by: Fabian Hugelshofer <hugelshofer2006@gmx.ch>
>>> They all seem fine to me, but a union might make it look
>>> a bit nicer :)
[...]
> Please, use union wherever it is possible. BTW, it seems to me that the
> conntrack-tools may suffer from the same portability problem. The
> (supposed) fix, which is attached, is ugly but union does not help since
> the size of struct nf_conntrack is not known. I do not find a way to do
> this cleanly without removing the use of the stack for temporary object
> allocation.
As you noted, conntrack-tools can be affected as well. I did not have a
look at it before, beacause I don't use it.
I don't see another way with the stack either. Dynamic memory allocation
would help, but is not nicer either.
Do you want me to rewrite the patches for libnetfilter-(log|contrack) in
the union style? I probably would put the union declaration in the file
scope rather than anonymous declarations in the function scope, because
it is the same everywhere.
next prev parent reply other threads:[~2008-06-05 12:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-03 10:20 [PATCH 1/3] libnfnetlink byte alignment Fabian Hugelshofer
2008-06-03 13:06 ` Patrick McHardy
2008-06-04 8:53 ` Fabian Hugelshofer
2008-06-04 14:35 ` Patrick McHardy
2008-06-04 21:42 ` Pablo Neira Ayuso
2008-06-05 12:55 ` Fabian Hugelshofer [this message]
2008-06-05 13:31 ` Pablo Neira Ayuso
2008-06-18 12:39 ` Pablo Neira Ayuso
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=4847E22E.8010701@gmx.ch \
--to=hugelshofer2006@gmx.ch \
--cc=kaber@trash.net \
--cc=netfilter-devel@vger.kernel.org \
--cc=pablo@netfilter.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.