On Fri, Feb 13, 2009 at 6:43 PM, pat-lkml <pat-lkml@xxxxxxxxx> wrote: > Luis R. Rodriguez wrote: >> On Fri, Feb 13, 2009 at 4:54 AM, Vitja Makarov <vitja.makarov@xxxxxxxxx> wrote: >>> This should be problem for 2.6.27 too. >> >> modified for 27 and applied, thanks > > I didn't run into this problem with 2.6.28-gentoo-r1... I've been running > compat-wireless from git since the 4th on this kernel, with no mac80211 > enabled and had no problems. Oh interesting, because skb->do_not_encrypt was there on 27, and skb->requeue was added as of 28. Since config.mk was enforcing it to be enabled and since compat-wireless uses its own include/linux/compat_autoconf.h with values derived from config.mk when building compat-wireless you were getting #define CONFIG_MAC80211 1 and therefore compat-wireless did build correctly assuming your kernel's skb_buff had skb->do_not_encrypt and skb->requeue although the reality of it is that it didn't therefore probably forcing mac80211 to mess around with other nearby fields in the skb_buff like the skb->dma_cookie, skb->secmark or skb->mark, depending on whether CONFIG_NET_DMA, CONFIG_NETWORK_SECMARK or neither were enabled respectively. So it seems it was working by chance as your kernel's skbs were being raped by mac80211 in their sleep. > Is there interest in a patch allowing you to > set something like FORCE=y on the CLI to override these patches? Do you have CONFIG_NET_DMA? If not do you have CONFIG_NETWORK_SECMARK? It'd be interesting to see what net core is doing due to the rape and it'd be even more interesting if we can determine the rape is allowed during certain circumstances, therefore allowing us to hack config.mk to allow for such atrocities to go on. Luis -- 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
