From mboxrd@z Thu Jan 1 00:00:00 1970 From: Johannes Berg Subject: Re: regression: tethering fails in 3.5 with iwlwifi Date: Thu, 21 Mar 2013 20:34:11 +0100 Message-ID: <1363894451.8181.4.camel@jlt4.sipsolutions.net> References: <1347361823.26457.3.camel@sauron.fi.intel.com> <1DC40B07CD6EC041A66726C271A73AE6195AE9C8@IRSMSX102.ger.corp.intel.com> <1347631355.5263.19.camel@sauron.fi.intel.com> <1347640763.5263.24.camel@sauron.fi.intel.com> <1347892887.7112.9.camel@sauron.fi.intel.com> (sfid-20120917_163617_677167_0B529F43) Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Eric Dumazet , linux-wireless@vger.kernel.org, netdev@vger.kernel.org, stable@vger.kernel.org To: artem.bityutskiy@linux.intel.com, patrik.flykt@intel.com Return-path: In-Reply-To: <1347892887.7112.9.camel@sauron.fi.intel.com> (sfid-20120917_163617_677167_0B529F43) Sender: stable-owner@vger.kernel.org List-Id: netdev.vger.kernel.org On Mon, 2012-09-17 at 17:41 +0300, Artem Bityutskiy wrote: > 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 I got back to this for a customer running 3.5, and after many failed attempts realized that you have to have iptables for this problem to actually happen. I reverse-bisected that the *fix* is 6caab7b0544e83e6c160b5e80f5a4a7dd69545c7, in 3.7. Is there still any stable kernel 3.5/3.6 (or possibly before, though for iwlwifi before doesn't matter) that this should be applied to? johannes