#74: module unstable on x86_64
------------------------------+---------------------------------------------
Reporter: kelmo | Owner:
Type: defect | Status: new
Priority: critical | Milestone: version 1.0.0 - first stable
release
Component: madwifi: driver | Version: trunk
Resolution: | Keywords:
------------------------------+---------------------------------------------
Comment (by anonymous):
Well, an->an_node.ni_uapsd_maxsp is 0, so, UAPSD is not active anyway. I
don't know why, perhaps just my setup.
Now, here is my chain of reasoning for this little patch:[[BR]]
1) M_UAPSD is a MadWifi-specific flag. It is not known to the rest of
Linux.[[BR]]
2) It seems like ieee80211_hardstart is the first entry point for any
packet into madwifi driver. Which means that any madwifi-specific flag set
before this function is meaningless.[[BR]]
3) The flags are kept in skb->cb which is described like this in skbuff.h:
''Control buffer. Free for use by every layer. Put private vars here''
From all of this I concluded, that any content of skb->cb at the very
start of ieee80211_hardstart must be something left by the previous layers
and have no meaning to madwifi. Perhaps it makes sense to simply memset
the whole thing to 0, but it would use more CPU clocks.
Now, all this have to be run by some of MadWifi devs to check if my
conclusions are correct. After all, I'm not a kernel hacker.
--
Ticket URL: <http://madwifi.org/ticket/74>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
