Hi I would say some part of the stack assumes a header (I dont know wich one ?) is pulled in skb->head/data, and thats a bug. Always use pskb_may_pull(skb, XXX) to make sure you can access XXX bytes in skb->data It would help if you describe the problem, because I have no history ( I am not linux-wireless subscriber). On Mon, Sep 17, 2012 at 4:41 PM, Artem Bityutskiy <artem.bityutskiy@xxxxxxxxxxxxxxx> wrote: > On Fri, 2012-09-14 at 19:39 +0300, Artem Bityutskiy wrote: >> On Fri, 2012-09-14 at 17:02 +0300, Artem Bityutskiy wrote: >> > Hi Johannes, >> > >> > We are using iwlwifi driver in Tizen IVI. We were using kernel v3.4 and >> > wifi tethering worked fine. But after upgrading to v3.5 it stopped >> > working. >> > >> > I am trying to bisect this already many hours - very difficult, because >> > tethering did not work in kernels around v3.4-rcX for some different >> > reasons, so just 'git bisect' does not work. >> >> OK, my latest finding is: >> >> bad: 3edaf3e Johannes Berg mac80211: manage AP netdev carrier state >> good: fe40cb6 Ashok Nagarajan mac80211: Check basic rates when peering >> >> However, just reverting in 3.5 does not solve the issue. I am out of >> ideas how to proceed. > > OK, finally I got it. After 3 days of hardcore intelligent bisecting > I've found out that tethering in 3.5 works for me if I revert > these 2 > patches: > > 56138f5 iwlwifi: dont pull too much payload in skb head > 3edaf3e mac80211: manage AP netdev carrier state > > Johannes, Eric? > > -- > Best Regards, > Artem Bityutskiy -- 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
