From: Johannes Berg <johannes@sipsolutions.net>
To: jt@hpl.hp.com
Cc: Michael Buesch <mb@bu3sch.de>,
linux-wireless@vger.kernel.org, netdev <netdev@vger.kernel.org>,
Jeff Garzik <jgarzik@pobox.com>, Dan Williams <dcbw@redhat.com>,
Jouni Malinen <jkm@devicescape.com>
Subject: Re: wireless extensions vs. 64-bit architectures
Date: Thu, 08 Mar 2007 20:23:26 +0100 [thread overview]
Message-ID: <1173381806.3248.58.camel@johannes.berg> (raw)
In-Reply-To: <20070308191322.GA24598@bougret.hpl.hp.com>
[-- Attachment #1: Type: text/plain, Size: 908 bytes --]
On Thu, 2007-03-08 at 11:13 -0800, Jean Tourrilhes wrote:
> I'm looking into that. The good thing is that we have
> redundant information, so we can check that things don't match. It's a
> bit more complex because some of those take variable parameters.
Yeah, and it also only happens with those event streams I think. But I
haven't checked other possible places.
> > I'd think this is a kernel bug and 32-bit userspace should rightfully be
> > able to expect 32-bit aligned structs, no? Actually fixing it in the
> > kernel would not be trivial though.
>
> What we could do is have every 64 bit kernel return things on
> a 32 bit boundary, irrespective of userspace used. That would break
> current 64 bit userspace.
Yeah, the only way to fix the bug without breaking that would be to
return different structs for the different userspaces which sounds
really complex.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]
next prev parent reply other threads:[~2007-03-08 19:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 1:27 wireless extensions vs. 64-bit architectures Johannes Berg
2007-03-06 14:31 ` Johannes Berg
2007-03-06 17:13 ` Jean Tourrilhes
2007-03-06 18:43 ` Michael Buesch
2007-03-07 1:42 ` Jean Tourrilhes
2007-03-07 2:03 ` Jean Tourrilhes
2007-03-08 14:39 ` Johannes Berg
2007-03-08 16:51 ` Johannes Berg
2007-03-08 17:37 ` Johannes Berg
2007-03-08 18:49 ` Jean Tourrilhes
2007-03-08 19:08 ` Johannes Berg
2007-03-08 19:13 ` Jean Tourrilhes
2007-03-08 19:23 ` Johannes Berg [this message]
2007-03-08 19:27 ` Johannes Berg
2007-03-08 19:34 ` Jouni Malinen
2007-03-08 19:40 ` Johannes Berg
2007-03-08 22:11 ` Jean Tourrilhes
2007-03-08 22:17 ` Randy Dunlap
2007-03-08 22:30 ` Jean Tourrilhes
2007-03-08 22:36 ` Johannes Berg
2007-03-08 22:34 ` David Miller
2007-03-08 22:49 ` Pavel Roskin
2007-03-08 22:22 ` Johannes Berg
2007-03-08 22:36 ` Jean Tourrilhes
2007-03-08 22:35 ` Johannes Berg
2007-03-09 21:35 ` Jean Tourrilhes
2007-03-09 23:19 ` Jouni Malinen
2007-03-10 1:01 ` Jean Tourrilhes
2007-03-11 17:40 ` Johannes Berg
2007-03-11 20:11 ` Ulrich Kunitz
2007-03-11 20:30 ` Michael Buesch
2007-03-12 17:56 ` Jean Tourrilhes
2007-03-12 18:21 ` Jouni Malinen
2007-03-12 20:34 ` Jean Tourrilhes
2007-03-13 19:42 ` Johannes Berg
2007-03-13 21:30 ` Jean Tourrilhes
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=1173381806.3248.58.camel@johannes.berg \
--to=johannes@sipsolutions.net \
--cc=dcbw@redhat.com \
--cc=jgarzik@pobox.com \
--cc=jkm@devicescape.com \
--cc=jt@hpl.hp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
--cc=netdev@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).