On 09/05/2012 04:13 PM, Johannes Berg wrote:
On Fri, 2012-08-24 at 14:43 +0200, Arend van Spriel wrote:
The wext code checks is the event data is within size limits.
When this check fails a message is logged with violating size.
This patch adds the event id to put us on the right track for
resolving that violation.
Reviewed-by: Hante Meuleman <meuleman@xxxxxxxxxxxx>
Signed-off-by: Arend van Spriel <arend@xxxxxxxxxxxx>
---
Maybe wext is not popular, but I found the change helpful debugging
so others may benefit from it. Still some wireless apps default to
it, eg. wpa_supplicant.
I don't even want to know what you're debugging, but I applied it
anyway.
FWIW, wext isn't just "not popular", it's "pretty much dead" :-)
johannes
We got the "Wireless Event too big" message and were wondering what
event from our driver was causing it. I agree wext is pretty much dead
although wpa_supplicant still defaults to that driver. At least in most
distro's it seems to be so.
Gr. AvS
--
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
