From: Alexander Aring <alex.aring@gmail.com>
To: Simon Vincent <simon.vincent@xsilon.com>
Cc: linux-wpan@vger.kernel.org
Subject: Re: Kernel crash when using multiple interfaces
Date: Fri, 15 May 2015 17:23:09 +0200 [thread overview]
Message-ID: <20150515152305.GB11157@omega> (raw)
In-Reply-To: <55560A88.1050903@xsilon.com>
On Fri, May 15, 2015 at 04:02:32PM +0100, Simon Vincent wrote:
> I tried the solution you proposed but it did not work, it resulted in a
> kernel crash (bad paging request).
>
okay, then simple send a patch with your solution. This should only
affect driver which using xmit_sync callback anyway.
I will notice a point at your previous work.
> We require multiple 802.15.4 interfaces for routing between different
> 802.15.4 networks. We have a 802.15.4 powerline phy (Hanadu [1]) and a
> 802.15.4 radio phy (MRF24J40). On some boxes we have both phys and route
> using RPL between the powerline and radio networks.
>
Okay, then we don't talking about multiple interfaces. We talking about
multiple phy's and that's when the issue occurs, because we have
multiple ieee802154_hw but one global ieee802154_xmit_cb.
My patch should define ieee802154_xmit_cb per ieee802154_hw instead.
Don't know what's your current issue is.
The ieee802154_xmit_cb is protected then by stop/wake queue which
garantuees that this struct isn't used twice (in case of multiple
interfaces), for multiple phy this is currently a bug.
- Alex
next prev parent reply other threads:[~2015-05-15 15:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-15 12:54 Kernel crash when using multiple interfaces Simon Vincent
2015-05-15 14:20 ` Alexander Aring
2015-05-15 15:02 ` Simon Vincent
2015-05-15 15:23 ` Alexander Aring [this message]
2015-05-16 15:33 ` Alexander Aring
2015-05-18 10:57 ` Simon Vincent
2015-05-18 14:00 ` Alexander Aring
2015-05-18 15:05 ` Simon Vincent
2015-05-18 15:37 ` Alexander Aring
2015-05-18 16:27 ` Alexander Aring
2015-05-19 11:18 ` Simon Vincent
2015-05-15 15:28 ` Alexander Aring
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=20150515152305.GB11157@omega \
--to=alex.aring@gmail.com \
--cc=linux-wpan@vger.kernel.org \
--cc=simon.vincent@xsilon.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).