linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kalle.valo@iki.fi>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: reinette chatre <reinette.chatre@intel.com>,
	Johannes Berg <johannes@sipsolutions.net>,
	John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>,
	"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH v4] cfg80211: validate channel settings across interfaces
Date: Sat, 08 Aug 2009 23:10:51 +0300	[thread overview]
Message-ID: <87r5vmkqwk.fsf@litku.valot.fi> (raw)
In-Reply-To: <4A7DD307.6090209@lwfinger.net> (Larry Finger's message of "Sat\, 08 Aug 2009 14\:33\:27 -0500")

Larry Finger <Larry.Finger@lwfinger.net> writes:

>> For example, when I run:
>> $ iwconfig wlan0 channel <ch> essid <essid>
>> 
>> then the command prompt never returns and system becomes progressively
>> unresponsive. The logs do not contain any details of the problem.
>
> I have the same problem here as well.

This patch fixes the issue:

commit 21e433f9ea04c319cc12b4094f292a8f1ad709e9
Author: Johannes Berg <johannes@sipsolutions.net>
Date:   Sat Aug 8 11:03:58 2009 +0200

    cfg80211: fix locking for SIWFREQ

Johannes sent it to the list this today and it's not in wireless-testing
yet.

-- 
Kalle Valo

      reply	other threads:[~2009-08-08 20:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07 12:47 [PATCH] cfg80211: validate channel settings across interfaces Johannes Berg
2009-08-07 12:50 ` [PATCH v2] " Johannes Berg
2009-08-07 13:49   ` [PATCH v3] " Johannes Berg
2009-08-07 15:22     ` [PATCH v4] " Johannes Berg
2009-08-08  6:19       ` reinette chatre
2009-08-08  8:43         ` Johannes Berg
2009-08-08  8:49         ` Kalle Valo
2009-08-08 19:33         ` Larry Finger
2009-08-08 20:10           ` Kalle Valo [this message]

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=87r5vmkqwk.fsf@litku.valot.fi \
    --to=kalle.valo@iki.fi \
    --cc=Larry.Finger@lwfinger.net \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=mcgrof@gmail.com \
    --cc=reinette.chatre@intel.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).