From: Patrick McHardy <kaber@trash.net>
To: Arturo Borrero Gonzalez <arturo.borrero.glez@gmail.com>
Cc: Netfilter Development Mailing list
<netfilter-devel@vger.kernel.org>,
Pablo Neira Ayuso <pablo@netfilter.org>
Subject: Re: [nftables] testing at sparc
Date: Fri, 4 Apr 2014 14:05:04 +0200 [thread overview]
Message-ID: <20140404120504.GB27267@macbook.localnet> (raw)
In-Reply-To: <CAOkSjBjhsQ7wS4_0YMrcV0Mm5yKOSVh8rn+sg3JK5zTH2qhYDw@mail.gmail.com>
On Wed, Apr 02, 2014 at 06:23:03PM +0200, Arturo Borrero Gonzalez wrote:
> Hi there!
>
> I've been testing nftables at sparc, looking for endianess issues.
Great, I meant to do this for a long time.
> Unfortunately, weird things happened.
>
> Adding some rule:
>
> % nft add table filter
> % nft add chain filter input
> % nft add rule filter input tcp dport 22 counter
> % nft list table filter
> table ip filter {
> chain input {
> payload @th,16,16 0x0 [invalid type] counter packets 0 bytes 0
> }
> }
>
> However, matching happened when I generated some traffic.
So it appears we only have a problem in userspace? That's at least partially
good news. Could you provide access to that machine for debugging?
> Also, compiling the nft cli tool:
>
> % make
> -e CC src/main.c
> src/main.c: In function 'nft_netlink':
> src/main.c:176:2: warning: cast increases required alignment of target
> type [-Wcast-align]
It appears all of these originate from the list iterator macros.
I guess its container_of() and the cast to (type *)(char *)ptr ...
next prev parent reply other threads:[~2014-04-04 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-02 16:23 [nftables] testing at sparc Arturo Borrero Gonzalez
2014-04-04 12:05 ` Patrick McHardy [this message]
2014-04-11 15:20 ` [PATCH RFC] expression: fix constant expression allocation on big endian Patrick McHardy
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=20140404120504.GB27267@macbook.localnet \
--to=kaber@trash.net \
--cc=arturo.borrero.glez@gmail.com \
--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.