Return-path: Received: from s3.sipsolutions.net ([5.9.151.49]:60458 "EHLO sipsolutions.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965366AbdAKMGE (ORCPT ); Wed, 11 Jan 2017 07:06:04 -0500 Message-ID: <1484136355.29931.1.camel@sipsolutions.net> (sfid-20170111_130607_462780_57A78AF0) Subject: Re: [REGRESSION, bisect] mesh: SAE connection causes kernel crash From: Johannes Berg To: Cedric Izoard , Masashi Honma , "linux-wireless@vger.kernel.org" Date: Wed, 11 Jan 2017 13:05:55 +0100 In-Reply-To: <927a79f16e8c429da7a0d06f1bfb2567@ceva-dsp.com> References: <1484121737.23671.0.camel@sipsolutions.net> <1484125220.23671.1.camel@sipsolutions.net> <12d8a797-6c51-4a79-2820-1f9e2e72b2f5@gmail.com> <1484128809.23671.11.camel@sipsolutions.net> <670a7439-50b9-4f07-1d7d-cb915547562e@gmail.com> <1484132519.23671.12.camel@sipsolutions.net> <1dd6e9f3-5ad2-1138-8017-c0ab208d9f88@gmail.com> <927a79f16e8c429da7a0d06f1bfb2567@ceva-dsp.com> Content-Type: text/plain; charset="UTF-8" Mime-Version: 1.0 Sender: linux-wireless-owner@vger.kernel.org List-ID: > I made a quick test with dongle using ath9k_htc driver and I indeed > reproduce the issue. Thanks. > Here is the stack trace I get: > I added a trace before calling skb_copy_expand to get the headroom of > the buffer before the copy and the headroom asked by the driver. > > [   83.200261] MESH fwd: skb_headroom=154, needed headroom=24 Could you also add a similar trace just before calling drv_tx()? Maybe we're adding something else to this skb? I can't find anything in the ath9k_htc driver that's adding more than 23 bytes (it's advertising 24) but clearly the last 8 bytes here are failing: > [   83.200346] skbuff: skb_under_panic: text:ffffffffa034c028 len:154 > put:8 head:ffff880213422e00 data:ffff880213422dfa tail:0x94 end:0xc0 > dev: Maybe mac80211 is putting something else? It'd have to be johannes