linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Holger Schurig <holgerschurig@gmail.com>
To: linux-wireless@vger.kernel.org
Cc: Samuel Ortiz <sameo@linux.intel.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Dan Williams <dcbw@redhat.com>,
	Holger Schurig <holgerschurig@googlemail.com>
Subject: Re: [PATCH] libertas: cfg80211 support
Date: Thu, 4 Feb 2010 11:11:26 +0100	[thread overview]
Message-ID: <201002041111.26722.holgerschurig@gmail.com> (raw)
In-Reply-To: <20100202000934.GA19847@sortiz.org>

Hi Samuel !

You wrote this code:

> +static int lbs_cfg_del_key(struct wiphy *wiphy, struct net_device *netdev,
> +                          u8 key_index, const u8 *mac_addr)
> +{
> +       struct lbs_private *priv = wiphy_priv(wiphy);
> +
> +       lbs_deb_enter(LBS_DEB_CFG80211);
> +
> +       if (key_index < 3 && priv->wep_key_len[key_index]) {
> +               priv->wep_key_len[key_index] = 0;
> +               lbs_set_wep_keys(priv);
> +       }
> +
> +       lbs_deb_assoc("del_key: key_idx %d, mac_addr %pM\n",
> +                     key_index, mac_addr);
> +
> +       return 0;
> +}

while I had this a no-op. I had a long comment at this code,
where I wrote:

/*
 * I think can keep this a NO-OP, because:
 * - we clear all keys whenever we do lbs_cfg_connect() anyway
 * - neither "iw" nor "wpa_supplicant" won't call this during
 *   an ongoing connection
 * - TODO: but I have to check if this is still true when
 *   I set the AP to periodic re-keying
 * - we've not kzallec() something when we've added a key at
 *   lbs_cfg_connect() or lbs_cfg_add_key().
 *
 * This causes lbs_cfg_del_key() only called at disconnect time,
 * where we'd just waste time deleting a key that is not going
 * to be used anyway.
 */

Didn't you agree with that test?  Did any of the WPA/WPA2/WEP
connections broke for you?  I didn't saw any problems, even
when changing from WEP to WPA and back without reloading the
driver.

However, I haven't tested libertas+cfg with the wext-
compatibility thing, maybe it's needed then?  But I doubt
it, because of point one in my comment-list.

-- 
http://www.holgerschurig.de

  parent reply	other threads:[~2010-02-04 10:13 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  0:09 [PATCH] libertas: cfg80211 support Samuel Ortiz
2010-02-02 20:36 ` John W. Linville
2010-02-03  9:31   ` Holger Schurig
2010-02-03 12:04     ` Samuel Ortiz
2010-02-03 15:32       ` Holger Schurig
2010-02-03 20:30         ` Dan Williams
2010-02-04  7:28           ` Holger Schurig
2010-02-04 21:49             ` Dan Williams
2010-02-04  9:52 ` Holger Schurig
2010-02-11 12:01   ` Samuel Ortiz
2010-02-11 12:24     ` Holger Schurig
2010-02-04 10:11 ` Holger Schurig [this message]
2010-02-11 12:03   ` Samuel Ortiz
2010-02-04 13:44 ` [PATCH] libertas+cfg80211: better disconnect support Holger Schurig
2010-02-15 10:46 ` [PATCH] libertas: cfg80211 support Holger Schurig
     [not found]   ` <cdd918981002240005o1fa50956yfb2a692716c06a55@mail.gmail.com>
2010-02-24 23:35     ` Dan Williams
2010-02-25  8:42       ` David MOUSSAUD
2010-02-25  8:48         ` Johannes Berg
2010-02-25 18:05           ` Andrey Yurovsky
2010-03-07 17:32             ` Kalle Valo
2010-03-07 17:52               ` Gábor Stefanik
2010-02-24  8:22 ` David MOUSSAUD

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=201002041111.26722.holgerschurig@gmail.com \
    --to=holgerschurig@gmail.com \
    --cc=dcbw@redhat.com \
    --cc=holgerschurig@googlemail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=sameo@linux.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).