From: Michael Wu <flamingice@sourmilk.net>
To: Gertjan van Wingerde <gwingerde@kpnplanet.nl>
Cc: Jiri Benc <jbenc@suse.cz>, netdev@vger.kernel.org
Subject: Re: [PATCH] d80211: Only free WEP crypto ciphers when they have been allocated correctly.
Date: Sat, 6 Jan 2007 12:29:11 -0500 [thread overview]
Message-ID: <200701061229.16632.flamingice@sourmilk.net> (raw)
In-Reply-To: <459FD5C4.9070301@kpnplanet.nl>
[-- Attachment #1: Type: text/plain, Size: 1203 bytes --]
On Saturday 06 January 2007 12:00, Gertjan van Wingerde wrote:
> The d80211 stack still tries to free the WEP crypto ciphers, even when
> allocating them previously has failed.
Actually, the code might not even have tried to allocate them. The ciphers are
guaranteed to be allocated when the device is registered however, so we
should be able to free it safely on unregister.
Signed-off-by: Michael Wu <flamingice@sourmilk.net>
---
net/d80211/ieee80211.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/net/d80211/ieee80211.c b/net/d80211/ieee80211.c
index 6e10db5..926d160 100644
--- a/net/d80211/ieee80211.c
+++ b/net/d80211/ieee80211.c
@@ -4715,6 +4715,7 @@ void ieee80211_unregister_hw(struct ieee
skb_queue_purge(&local->skb_queue_unreliable);
ieee80211_dev_free_index(local);
+ ieee80211_wep_free(local);
ieee80211_led_exit(local);
}
EXPORT_SYMBOL(ieee80211_unregister_hw);
@@ -4724,7 +4725,6 @@ void ieee80211_free_hw(struct ieee80211_
struct ieee80211_local *local = hw_to_local(hw);
ieee80211_if_free(local->mdev);
- ieee80211_wep_free(local);
ieee80211_dev_free(local);
}
EXPORT_SYMBOL(ieee80211_free_hw);
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-01-06 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-06 17:00 [PATCH] d80211: Only free WEP crypto ciphers when they have been allocated correctly Gertjan van Wingerde
2007-01-06 17:29 ` Michael Wu [this message]
2007-01-06 18:14 ` Gertjan van Wingerde
2007-01-10 20:14 ` Jiri Benc
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=200701061229.16632.flamingice@sourmilk.net \
--to=flamingice@sourmilk.net \
--cc=gwingerde@kpnplanet.nl \
--cc=jbenc@suse.cz \
--cc=netdev@vger.kernel.org \
/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).