From: "Luis R. Rodriguez" <lrodriguez@atheros.com>
To: Michael Buesch <mb@bu3sch.de>
Cc: Luis Rodriguez <Luis.Rodriguez@Atheros.com>,
Jouni Malinen <Jouni.Malinen@Atheros.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: regulatory: Operation already in progress
Date: Sun, 25 Jan 2009 12:24:07 -0800 [thread overview]
Message-ID: <20090125202407.GJ22475@tesla> (raw)
In-Reply-To: <200901252105.37604.mb@bu3sch.de>
On Sun, Jan 25, 2009 at 12:05:37PM -0800, Michael Buesch wrote:
> On Sunday 25 January 2009 20:36:56 Luis R. Rodriguez wrote:
> > On Sun, Jan 25, 2009 at 10:45:17AM -0800, Luis Rodriguez wrote:
> > > On Sun, Jan 25, 2009 at 10:41:38AM -0800, Michael Buesch wrote:
> > > > On Sunday 25 January 2009 19:21:07 Luis R. Rodriguez wrote:
> > > > > On Sun, Jan 25, 2009 at 05:22:42AM -0800, Michael Buesch wrote:
> > > > > > mb@quimby:~/kernel$ sudo iw reg set DE
> > > > > > command failed: Operation already in progress (-114)
> > > > > >
> > > > > > I wonder why this happens.
> > > > > > What I just did was install 2.6.28.2 and install today's compat-wireless.
> > > > > >
> > > > > > In dmesg I can see it succeeded once but it doesn't work anymore now.
> > > > > > [ 973.992710] cfg80211: Calling CRDA for country: DE
> > > > > > [ 973.998576] cfg80211: Regulatory domain changed to country: DE
> > > > > > [ 973.998630] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> > > > > > [ 973.998691] (2400000 KHz - 2483500 KHz @ 40000 KHz), (N/A, 2000 mBm)
> > > > > > [ 973.998738] (5150000 KHz - 5255000 KHz @ 40000 KHz), (N/A, 2301 mBm)
> > > > > > [ 973.998785] (5470000 KHz - 5650000 KHz @ 40000 KHz), (N/A, 3000 mBm)
> > > > >
> > > > > Had you called twice?
> > > >
> > > > yeah, once manually with iw and once with hostapd.
> > > >
> > > > > If so we now tell userspace when its there by -EALREADY,
> > > > > we were just silently accepting two consecutive calls before.
> > > >
> > > > Well, but it makes hostapd fail.
> > > > I think it's a bit weird to throw and error code. In general most programs
> > > > silently return success early, if an operation was already done.
> > >
> > > We can prevent to propagate -EALREADY to userspace -- sure, I'll cook
> > > up the patch.
> >
> > Actually we could also patch hostapd to deal with -EALREADY as a success too.
> > Its either that or we have nl80211 return 0 instead of -EALREADY. Jouni, any
> > preference?
>
> I think returning an error doesn't make sense.
> All the set-regulatory nl80211 command does is "set the domain to X". So why does it
> fail, if it was already X before the call. All the caller wants is to select domain X.
> That's what he gets in any case. Whether it was set to X or not before the call shouldn't matter.
> It's also confusing to get a "command failed" from iw.
Yeah that is true, well I'll send a patch.
Luis
next prev parent reply other threads:[~2009-01-25 20:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 13:22 regulatory: Operation already in progress Michael Buesch
2009-01-25 18:21 ` Luis R. Rodriguez
2009-01-25 18:41 ` Michael Buesch
2009-01-25 18:45 ` Luis R. Rodriguez
2009-01-25 19:36 ` Luis R. Rodriguez
2009-01-25 20:05 ` Michael Buesch
2009-01-25 20:24 ` Luis R. Rodriguez [this message]
2009-01-25 20:34 ` Gábor Stefanik
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=20090125202407.GJ22475@tesla \
--to=lrodriguez@atheros.com \
--cc=Jouni.Malinen@Atheros.com \
--cc=Luis.Rodriguez@Atheros.com \
--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 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.