All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@medozas.de>
To: "Chini, Georg (HP App Services)" <georg.chini@hp.com>
Cc: "netfilter-devel@vger.kernel.org" <netfilter-devel@vger.kernel.org>
Subject: Re: Problem with ipset on sparc64
Date: Wed, 4 Nov 2009 23:08:15 +0100 (CET)	[thread overview]
Message-ID: <alpine.LSU.2.00.0911042258430.16456@obet.zrqbmnf.qr> (raw)
In-Reply-To: <4513233BE7DF454BB62D30017EEE55436CFB9228E4@GVW1115EXC.americas.hpqcorp.net>


On Wednesday 2009-11-04 22:50, Chini, Georg (HP App Services) wrote:
>>
>>I'm using ipset 3.2 on a sparc64 system (ultra2), kernel 2.6.31.5, Debian 5.
>>Everything works fine, but the -L option shows strange values for a portmap.
>
>
>If you explicitly compile ipset as a 64-bit program rather than the
>32-bit default that is used on sparc, will the correct values be
>shown?
>
>Thanks for the fast reply. I added -m64 to cc and ld options and
>recompiled. Is that correct? If yes, I now get a bus error instead
>of a wrong listing. Or do I have to change anything else?

Bus error means something was not quite correctly aligned
(yet another ipset bug).

The lack of cheap access to big-endian, alignment-sensitive hardware
means many codes do not get the testing they deserve :-/

To workaround the alignedness issue, you could take an x86_64 machine
and compile a strictly 32-bit ipset on it, and see whether the values
are also off.

  reply	other threads:[~2009-11-04 22:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-04 21:07 Problem with ipset on sparc64 Chini, Georg (HP App Services)
2009-11-04 21:19 ` Jan Engelhardt
2009-11-04 21:50   ` AW: " Chini, Georg (HP App Services)
2009-11-04 22:08     ` Jan Engelhardt [this message]
2009-11-05  8:31       ` Jozsef Kadlecsik
2009-11-05 10:36         ` Jozsef Kadlecsik
2009-11-05 11:06           ` Jan Engelhardt
2009-11-05 11:21             ` Jozsef Kadlecsik
2009-11-05 11:30               ` Jan Engelhardt
2009-11-05 17:57                 ` Another issue " Chini, Georg (HP App Services)
2009-11-05 18:38                   ` Jozsef Kadlecsik
2009-11-10 21:17                     ` Jozsef Kadlecsik
2009-11-11  6:51                       ` AW: " Chini, Georg (HP App Services)
2009-11-11 18:27                         ` Jozsef Kadlecsik
2009-11-05 18:36                 ` Problem " Jozsef Kadlecsik
2009-11-05 18:41                   ` Jan Engelhardt
2009-11-05 22:48                 ` David Miller
2009-11-05 20:03       ` Jozsef Kadlecsik
2009-11-05 20:10         ` Jan Engelhardt

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=alpine.LSU.2.00.0911042258430.16456@obet.zrqbmnf.qr \
    --to=jengelh@medozas.de \
    --cc=georg.chini@hp.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 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.