From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: xxiao <austinxxh-ath9k@yahoo.com>, linux-wireless@vger.kernel.org
Subject: Re: Status of 802.11s in wireless-testing?
Date: Wed, 05 Aug 2009 19:04:26 +0200 [thread overview]
Message-ID: <1249491866.6902.23.camel@johannes.local> (raw)
In-Reply-To: <20090805165021.GA20338@tuxdriver.com>
[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]
On Wed, 2009-08-05 at 12:50 -0400, John W. Linville wrote:
> On Wed, Aug 05, 2009 at 09:08:54AM -0700, xxiao wrote:
> > I didn't see patches from open80211s project for a while, which
> > means it will break as the rest mac80211/drivers are evolving quickly.
>
> You may be right, but it _should_not_ mean that -- at least not
> necessarily. Yes, there will be accidental breakage from time to time.
> But developers ought to keep mesh in mind when making changes and
> they should be "on the hook" to fix whatever breaks.
Right now, except from the stuff Luis had broken and fixed, the real
problem is that there are a bunch of bugs that appear to have been in
the code forever, just never noticed -- for instance the code can end up
calling synchronize_rcu() in an atomic section.
This is the reason for disabling it -- it can splatter all over the
scheduler if that happens, and it's not clear to me that it cannot
happen. It seems not to happen in _most_ scenarios, but I've certainly
caused it to happen by not beaconing, for instance.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2009-08-05 17:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2f1373ed0908042145pc83adc5qd968e3bf8d0ce3c7@mail.gmail.com>
2009-08-05 16:08 ` Status of 802.11s in wireless-testing? xxiao
2009-08-05 16:50 ` John W. Linville
2009-08-05 17:04 ` Johannes Berg [this message]
2009-08-05 17:49 ` Javier Cardona
2009-08-05 18:23 ` Johannes Berg
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=1249491866.6902.23.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=austinxxh-ath9k@yahoo.com \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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