From: Johannes Berg <johannes@sipsolutions.net>
To: Masashi Honma <masashi.honma@gmail.com>,
linux-wireless@vger.kernel.org, Cedric.Izoard@ceva-dsp.com
Subject: Re: [REGRESSION, bisect] mesh: SAE connection causes kernel crash
Date: Wed, 11 Jan 2017 09:02:17 +0100 [thread overview]
Message-ID: <1484121737.23671.0.camel@sipsolutions.net> (raw)
In-Reply-To: <b72bc51c-1873-6178-9990-7d9e99ee4b88@gmail.com> (sfid-20170111_003605_347505_85ADC15C)
On Wed, 2017-01-11 at 08:35 +0900, Masashi Honma wrote:
> I have encountered kernel crash when I have used mesh SAE
> connection
> with ath9k_htc device (Sony UWA-BR100). I have tried to connect 2
> peers
> to each other, then only one peer crashes.
>
> By bisect, this commit looks causes this issue.
>
> commit d8da0b5d64d58f7775a94bcf12dda50f13a76f22
> Author: Cedric Izoard <Cedric.Izoard@ceva-dsp.com>
> Date: Wed Dec 7 09:59:00 2016 +0000
>
> mac80211: Ensure enough headroom when forwarding mesh pkt
I don't think this makes sense - if you only have two peers then you
shouldn't even run into forwarding code paths?
johannes
next prev parent reply other threads:[~2017-01-11 8:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-10 23:35 [REGRESSION, bisect] mesh: SAE connection causes kernel crash Masashi Honma
2017-01-11 8:02 ` Johannes Berg [this message]
2017-01-11 8:50 ` Masashi Honma
2017-01-11 9:00 ` Johannes Berg
2017-01-11 9:38 ` Masashi Honma
2017-01-11 10:00 ` Johannes Berg
2017-01-11 10:36 ` Masashi Honma
2017-01-11 11:01 ` Johannes Berg
2017-01-11 11:10 ` Masashi Honma
2017-01-11 11:35 ` Cedric Izoard
2017-01-11 12:05 ` Johannes Berg
2017-01-11 13:22 ` Cedric Izoard
2017-01-11 13:34 ` Johannes Berg
2017-01-11 13:41 ` Cedric Izoard
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1484121737.23671.0.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=Cedric.Izoard@ceva-dsp.com \
--cc=linux-wireless@vger.kernel.org \
--cc=masashi.honma@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.