From: drago01 <drago01@gmail.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: "John Linville" <linville@tuxdriver.com>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: always insert key into list
Date: Sat, 1 Mar 2008 19:57:01 +0100 [thread overview]
Message-ID: <f6ca9fed0803011057k5e2999e1vbb8d69a7306d6f29@mail.gmail.com> (raw)
In-Reply-To: <1204396338.3917.9.camel@johannes.berg>
On Sat, Mar 1, 2008 at 7:32 PM, Johannes Berg <johannes@sipsolutions.net> wrote:
> Today I hit one of my new WARN_ONs in the mac80211 code because
> a key wasn't being freed correctly. After wondering for a while
> I finally tracked it to the fact that STA keys aren't added to
> the per-sdata key list correctly, they are supposed to always be
> on that list, not just for default keys. This patch fixes that.
can this be somehow related to the "wep decrypt failed" message that I
get when using dynamic wep?
(I didn't have time to create any additional debug info for it yet ...)
next prev parent reply other threads:[~2008-03-01 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-01 18:32 [PATCH] mac80211: always insert key into list Johannes Berg
2008-03-01 18:57 ` drago01 [this message]
2008-03-01 20:56 ` Johannes Berg
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=f6ca9fed0803011057k5e2999e1vbb8d69a7306d6f29@mail.gmail.com \
--to=drago01@gmail.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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