On Thu, Mar 08, 2007 at 08:08:29PM +0100, Johannes Berg wrote: > On Thu, 2007-03-08 at 10:49 -0800, Jean Tourrilhes wrote: > > > A proper fix would involve forcing the alignement in the > > kernel. Unfortunately, that would break 64bit->64bit configs. I think > > I can build a workaround for this in iwlib. > > Not easily I think. You'd have to get something that has a well-defined > result and see whether padding is present or not. The MAC address might > be good enough (due to len being 24 instead of the expected 20) though. > Thing is that it's really hard to figure out (even at runtime) whether > the kernel and machine are 64 or 32-bits. 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. > 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. > johannes Thanks ! Jean - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
