From: Evgeniy Polyakov <zbr@ioremap.net>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Jaswinder Singh Rajput <jaswinder@kernel.org>,
Patrick McHardy <kaber@trash.net>,
David Miller <davem@davemloft.net>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] headers_check fix: linux/netfilter/xt_osf.h
Date: Sun, 28 Jun 2009 13:56:37 +0400 [thread overview]
Message-ID: <20090628095637.GA651@ioremap.net> (raw)
In-Reply-To: <20090627220007.GB2719@uranus.ravnborg.org>
On Sun, Jun 28, 2009 at 12:00:07AM +0200, Sam Ravnborg (sam@ravnborg.org) wrote:
> What about the other potential issues in the same file?
> struct xt_osf_opt {
> __u16 kind, length;
> struct xt_osf_wc wc;
> };
>
> Do we know that struct xt_osf_wc is always aligned at a two byte
> address also on 64 bit?
Why 2 bytes? It is 4 bytes aligned everywhere everytime.
> Do we know that sizeof(struct xt_osf_opt) is the same
> on all platforms?
Yes.
> struct xt_osf_user_finger {
> struct xt_osf_wc wss;
>
> __u8 ttl, df;
> __u16 ss, mss;
> __u16 opt_num;
>
> char genre[MAXGENRELEN];
> char version[MAXGENRELEN];
> char subtype[MAXGENRELEN];
>
> /* MAX_IPOPTLEN is maximum if all options are NOPs or EOLs */
> struct xt_osf_opt opt[MAX_IPOPTLEN];
> };
>
> Do we know that opt[MAX_IPOPTLEN] always start at the same offset
> with different architectures?
Yes.
> struct xt_osf_nlmsg {
> struct xt_osf_user_finger f;
> struct iphdr ip;
> struct tcphdr tcp;
> };
>
> We do not knwo struct iphdr/tcphdr - missing include.
> Do we know the alignment of the above structs?
> Are they always the same on all archs?
You won't believe...
--
Evgeniy Polyakov
next prev parent reply other threads:[~2009-06-28 9:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-27 16:31 [PATCH] headers_check fix: linux/netfilter/xt_osf.h Jaswinder Singh Rajput
2009-06-27 17:52 ` Evgeniy Polyakov
2009-06-27 22:00 ` Sam Ravnborg
2009-06-28 5:18 ` Jaswinder Singh Rajput
2009-06-28 9:56 ` Evgeniy Polyakov [this message]
2009-06-29 12:29 ` 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=20090628095637.GA651@ioremap.net \
--to=zbr@ioremap.net \
--cc=davem@davemloft.net \
--cc=jaswinder@kernel.org \
--cc=kaber@trash.net \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.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.