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 10:00:20 +0100 [thread overview]
Message-ID: <1484125220.23671.1.camel@sipsolutions.net> (raw)
In-Reply-To: <aa60ffb2-b756-b807-4976-20f2eca6665d@gmail.com> (sfid-20170111_095056_507074_72EC4D80)
On Wed, 2017-01-11 at 17:50 +0900, Masashi Honma wrote:
> On 2017年01月11日 17:02, Johannes Berg wrote:
> > I don't think this makes sense - if you only have two peers then
> > you
> > shouldn't even run into forwarding code paths?
> >
> > johannes
>
> Though it looks odd, the code has run into forwarding code path even
> though peer to peer mesh connection.
>
> fwd_skb = skb_copy(skb, GFP_ATOMIC);
>
> I checked it with printk().
>
> # I know printk() should not be used in the context, just for
> checking.
Ok, that's strange, but maybe there's a reason.
Can you extract *any* information whatsoever? Like maybe if you switch
to a VT console before running into the crash? I don't have any
hardware to run this on, and hwsim doesn't have any issues.
johannes
next prev parent reply other threads:[~2017-01-11 9:00 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
2017-01-11 8:50 ` Masashi Honma
2017-01-11 9:00 ` Johannes Berg [this message]
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=1484125220.23671.1.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.