From: Jiri Benc <jbenc@suse.cz>
To: Michael Wu <flamingice@sourmilk.net>
Cc: Gertjan van Wingerde <gwingerde@kpnplanet.nl>, netdev@vger.kernel.org
Subject: Re: [PATCH] d80211: Only free WEP crypto ciphers when they have been allocated correctly.
Date: Wed, 10 Jan 2007 21:14:22 +0100 [thread overview]
Message-ID: <20070110211422.1acd6bca@griffin.suse.cz> (raw)
In-Reply-To: <200701061229.16632.flamingice@sourmilk.net>
On Sat, 6 Jan 2007 12:29:11 -0500, Michael Wu wrote:
> 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.
Applied to my tree, thanks for the patch.
Jiri
--
Jiri Benc
SUSE Labs
prev parent reply other threads:[~2007-01-10 20:14 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
2007-01-06 18:14 ` Gertjan van Wingerde
2007-01-10 20:14 ` Jiri Benc [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=20070110211422.1acd6bca@griffin.suse.cz \
--to=jbenc@suse.cz \
--cc=flamingice@sourmilk.net \
--cc=gwingerde@kpnplanet.nl \
--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).