All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: Fabian Hugelshofer <hugelshofer2006@gmx.ch>
Cc: netfilter-devel@vger.kernel.org
Subject: Re: [PATCH] netfilter ulog byte alignment problem
Date: Tue, 03 Jun 2008 15:04:35 +0200	[thread overview]
Message-ID: <48454163.1060700@trash.net> (raw)
In-Reply-To: <1212426348.31217.30.camel@pumper.lan.luxnet.ch>

Fabian Hugelshofer wrote:
> I am using libipulog on an XScale IXP422 processor (big endian ARM). I
> call ipulog_get_packet to decode the multipart message and then access
> the fields in the packet (ulog_packet_msg_t). Accessing fields 'mac' and
> 'payload' does not give me the right data. The data is actually there,
> but an access to the arrays ends up at a wrong location. Manually adding
> an offset leads to the correct position (e.g. pkt->payload[-66] instead
> of pkt->payload[0] for the first byte of the IP packet).
> 
> I tracked the issue down to a byte alignment problem in
> ulog_packet_msg_t (include/linux/netfilter_ipv4/ipt_ULOG.h). Setting
> attributes 'packed' or 'aligned' or using 'size_t' instead of 'unsigned
> char' for field 'mac_len' solved the problem. It seems necessary to help
> the compiler doing things right.
> 
> This patch requires applications to be recompiled against the new header
> file. Let me know what you think.

I'm afraid it might break compatibility on other architectures.
Are your userspace and kernel compiled using the same options?
Why would they lay out the structure differently?

  reply	other threads:[~2008-06-03 13:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 17:05 [PATCH] netfilter ulog byte alignment problem Fabian Hugelshofer
2008-06-03 13:04 ` Patrick McHardy [this message]
2008-06-04  8:43   ` Fabian Hugelshofer

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=48454163.1060700@trash.net \
    --to=kaber@trash.net \
    --cc=hugelshofer2006@gmx.ch \
    --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.