From: "David S. Miller" <davem@redhat.com>
To: James Bottomley <James.Bottomley@steeleye.com>
Cc: Arnaldo Carvalho de Melo <acme@conectiva.com.br>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: New struct sock_common breaks parisc 64 bit compiles with a misalignment
Date: 14 Jun 2003 23:19:06 -0700 [thread overview]
Message-ID: <1055657946.6481.6.camel@rth.ninka.net> (raw)
In-Reply-To: <1055221067.11728.14.camel@mulgrave>
On Mon, 2003-06-09 at 21:57, James Bottomley wrote:
> The problem seems to be that the new struct sock_common ends with a
> pointer and an atomic_t (which is an int on parisc), so the compiler
> adds an extra four bytes of padding where none previously existed in
> struct tcp_tw_bucket, so the __u64 ptr tricks with tw_daddr fail.
I'm fixing this, but why does it "fail"? You should get unaligned
traps which get fixed up by the trap handler.
If that isn't happening, lots of things in the networking should
break on you.
--
David S. Miller <davem@redhat.com>
next prev parent reply other threads:[~2003-06-15 6:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 4:57 New struct sock_common breaks parisc 64 bit compiles with a misalignment James Bottomley
2003-06-10 16:12 ` David S. Miller
2003-06-15 17:09 ` YOSHIFUJI Hideaki / 吉藤英明
2003-06-15 17:06 ` David S. Miller
2003-06-15 6:19 ` David S. Miller [this message]
2003-06-15 14:35 ` James Bottomley
2003-06-15 14:35 ` David S. Miller
2003-06-15 15:17 ` James Bottomley
2003-06-15 15:23 ` David S. Miller
[not found] <1055687753.10803.28.camel@mulgrave.suse.lists.linux.kernel>
[not found] ` <20030615.073503.112613460.davem@redhat.com.suse.lists.linux.kernel>
[not found] ` <1055690231.10803.54.camel@mulgrave.suse.lists.linux.kernel>
[not found] ` <20030615.082355.08334189.davem@redhat.com.suse.lists.linux.kernel>
2003-06-15 15:41 ` Andi Kleen
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=1055657946.6481.6.camel@rth.ninka.net \
--to=davem@redhat.com \
--cc=James.Bottomley@steeleye.com \
--cc=acme@conectiva.com.br \
--cc=linux-kernel@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.