From: Jouni Malinen <j@w1.fi>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Dave <kilroyd@googlemail.com>,
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 21:22:13 +0300 [thread overview]
Message-ID: <20081006182213.GH4941@jm.kir.nu> (raw)
In-Reply-To: <20081006175357.GB3448@tuxdriver.com>
On Mon, Oct 06, 2008 at 01:53:57PM -0400, John W. Linville wrote:
> 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?
IWEVCUSTOM is the wrong way of doing this. However, the problem here is
that IWEVASSOCREQIE and IWEVASSOCRESPIE can trigger wpa_supplicant to
behave incorrectly in 64-bit kernel, 32-bit userspace case (64/64 and
32/32 work fine). This is worked around in the current 0.6.x devel
branch, but not in any of the released versions.
--
Jouni Malinen PGP id EFC895FA
prev parent reply other threads:[~2008-10-06 18:23 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
2008-10-06 18:22 ` Jouni Malinen [this message]
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=20081006182213.GH4941@jm.kir.nu \
--to=j@w1.fi \
--cc=jouni.malinen@atheros.com \
--cc=kilroyd@googlemail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
/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.