From: Johannes Berg <johannes@sipsolutions.net>
To: Michael Buesch <mb@bu3sch.de>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [RFT] mac80211: allow mode changes while interface is up
Date: Sat, 21 Mar 2009 17:56:53 +0100 [thread overview]
Message-ID: <1237654613.5100.312.camel@johannes.local> (raw)
In-Reply-To: <200903211745.06974.mb@bu3sch.de>
[-- Attachment #1: Type: text/plain, Size: 901 bytes --]
On Sat, 2009-03-21 at 17:45 +0100, Michael Buesch wrote:
> > - return 0;
> > + if (running) {
> > + ret = ieee80211_open(sdata->dev);
> > + if (ret) {
> > + /*
> > + * ieee80211_open could fail, for example if the user
> > + * wants to have an interface combination now that we
> > + * do not support -- in that case roll back. This has
> > + * to succeed unless we have a driver/mac80211 bug,
> > + * since the interface was there before!
>
> What about memory allocation failures?
> I think we should check for an error and if one occurs take the interface
> completely down and return the error to userspace.
Makes sense, need to audit the code though to verify that
ieee80211_stop() doesn't puke if you call it twice in a row (since
dev_close() will call it again)
It's only proof-of-concept code -- like I said, I have no interest in
it.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2009-03-21 16:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-21 16:39 [RFT] mac80211: allow mode changes while interface is up Johannes Berg
2009-03-21 16:45 ` Michael Buesch
2009-03-21 16:56 ` Johannes Berg [this message]
2009-03-21 17:13 ` 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=1237654613.5100.312.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).