Return-path: Received: from madara.hpl.hp.com ([192.6.19.124]:63034 "EHLO madara.hpl.hp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933651AbXCMVcd (ORCPT ); Tue, 13 Mar 2007 17:32:33 -0400 Date: Tue, 13 Mar 2007 14:30:50 -0700 To: Johannes Berg Cc: Jouni Malinen , Michael Buesch , linux-wireless@vger.kernel.org, netdev , Jeff Garzik , Dan Williams Subject: Re: wireless extensions vs. 64-bit architectures Message-ID: <20070313213050.GB6272@bougret.hpl.hp.com> Reply-To: jt@hpl.hp.com References: <20070308184954.GA24485@bougret.hpl.hp.com> <1173382042.3248.63.camel@johannes.berg> <20070308193412.GG23040@devicescape.com> <1173382802.3248.68.camel@johannes.berg> <20070308221128.GA24884@bougret.hpl.hp.com> <1173393326.3831.21.camel@johannes.berg> <20070309213531.GA28070@bougret.hpl.hp.com> <1173634801.3382.8.camel@johannes.berg> <20070312175639.GA4048@bougret.hpl.hp.com> <1173814925.12717.6.camel@johannes.berg> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <1173814925.12717.6.camel@johannes.berg> From: Jean Tourrilhes Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Mar 13, 2007 at 08:42:05PM +0100, Johannes Berg wrote: > On Mon, 2007-03-12 at 10:56 -0700, Jean Tourrilhes wrote: > > > I did that in the e-mail to Jouni. The problem is that most > > people are unfamiliar with decoding iwevents, so can't grasp the > > explanation. > > Basically, for iwpoint, we have an outer lenght and an inner > > length. If they don't match, we have an alignement issue and just need > > to pick the payload 8 bytes after the expected location. > > For other events, they have a well known size. If the outer > > lenght is not the expected size, but is expected+4, you just pick the > > payload 4 bytes after the expected location. > > Ok. > > So the plan now is to put this document up somewhere maybe with some > graphics or whatever, and then send this to distros so they know what > happens when people hit this bug. > > Does your new version work without padding even on 64-bit arches? Then > in a few years we can actually remove the padding completely in the > kernel, right? You are too smart ;-) Yes, the second version in pre16 does exactly that. That's why I had to change the constants. > johannes Jean