linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Dave <kilroyd@googlemail.com>
Cc: linux-wireless@vger.kernel.org,
	Jouni Malinen <jouni.malinen@atheros.com>
Subject: Re: [PATCH] mac80211: avoid "Wireless Event too big" message for assoc response
Date: Mon, 6 Oct 2008 13:53:57 -0400	[thread overview]
Message-ID: <20081006175357.GB3448@tuxdriver.com> (raw)
In-Reply-To: <48E53C1F.4040909@gmail.com>

On Thu, Oct 02, 2008 at 10:24:47PM +0100, Dave wrote:
> John W. Linville wrote:
>> An attempt was made by Jouni Malinen to correct this issue by
>> converting to use IWEVASSOCREQIE and IWEVASSOCRESPIE messages instead
>> ("mac80211: Use IWEVASSOCREQIE instead of IWEVCUSTOM").  Unfortunately,
>> that caused a problem due to 32-/64-bit interactions on some systems and
>> was reverted after the 'userland ABI' rule was invoked.
>
> I was unaware of this, and used IWEVASSOCREQIE and IWEVASSOCRESPIE in the
> orinoco wpa updates since the events were available in linux/wireless.h.
>
> Should I post a patch to use IWEVCUSTOM instead?

Honestly, I don't know.  I think we would prefer not to use the
IWEVCUSTOM method, but my memory is not 100% clear on what triggered
the 32-/64-bit problem.  Perhaps Jouni can comment?

John
-- 
John W. Linville		Linux should be at the core
linville@tuxdriver.com			of your literate lifestyle.

  reply	other threads:[~2008-10-06 17:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 19:45 [PATCH] mac80211: avoid "Wireless Event too big" message for assoc response John W. Linville
2008-10-02 21:24 ` Dave
2008-10-06 17:53   ` John W. Linville [this message]
2008-10-06 18:22     ` Jouni Malinen

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=20081006175357.GB3448@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=jouni.malinen@atheros.com \
    --cc=kilroyd@googlemail.com \
    --cc=linux-wireless@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).