From: Harald Welte <laforge@netfilter.org>
To: Jouni Malinen <jkmaline@cc.hut.fi>
Cc: David Miller <davem@davemloft.net>,
Netfilter Development Mailinglist
<netfilter-devel@lists.netfilter.org>,
Linux Netdev List <netdev@vger.kernel.org>,
linux-kernel@vger.kernel.org, bunk@stusta.de
Subject: Re: [PATCH 2/2] [NETFILTER] remove bogus hand-coded htonll()
Date: Sun, 4 Sep 2005 06:10:24 +0200 [thread overview]
Message-ID: <20050904041024.GJ4415@rama.de.gnumonks.org> (raw)
In-Reply-To: <20050903165425.GZ7781@jm.kir.nu>
[-- Attachment #1: Type: text/plain, Size: 1606 bytes --]
On Sat, Sep 03, 2005 at 09:54:25AM -0700, Jouni Malinen wrote:
> On Sat, Sep 03, 2005 at 10:43:15AM +0200, Harald Welte wrote:
>
> > htonll() is nothing else than cpu_to_be64(), so we'd rather call the
> > latter.
>
> Actually, the htonll() implementation does not seem to be doing what
> cpu_to_be64() is doing.. However, I would assume this is a bug in
> htonll() and this change to use cpu_to_be64() is fixing that.
ACK.
> Can this bug cause any major problems in the current implementation?
the "current implementation" was only merged after 2.6.13 is released,
so I doubt anyone but the netfilter developers is using it yet.
> I would assume that the first index should have had '-i' added to it, if
> the purpose is to swap byte order.. The code here is leaving some
> arbitrary data in 7 bytes of the 64-bit variable and setting
> (u8*)&out[7] = (u8*)&in[7] in somewhat inefficient way ;-). In addition,
> this looks more like swap-8-bytes-unconditionally than doing this based
> on host byte order..
yes, yes, yes. Somehow this ancient buggy implementation slipped into
mainline. I know I had fixed this before.
So please let's all forget about this embarrassing htonll() and move on.
--
- Harald Welte <laforge@netfilter.org> http://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: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-09-04 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-03 8:43 [PATCH 2/2] [NETFILTER] remove bogus hand-coded htonll() Harald Welte
2005-09-03 16:54 ` Jouni Malinen
2005-09-04 4:10 ` Harald Welte [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=20050904041024.GJ4415@rama.de.gnumonks.org \
--to=laforge@netfilter.org \
--cc=bunk@stusta.de \
--cc=davem@davemloft.net \
--cc=jkmaline@cc.hut.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@lists.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox