From: Johannes Berg <johannes@sipsolutions.net>
To: reinette chatre <reinette.chatre@intel.com>
Cc: "linville@tuxdriver.com" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Winkler, Tomas" <tomas.winkler@intel.com>
Subject: Re: [PATCH v2.6.29] iwlwifi: clean key table in iwl_clear_stations_table
Date: Wed, 28 Jan 2009 22:35:54 +0100 [thread overview]
Message-ID: <1233178554.16048.50.camel@johannes.local> (raw)
In-Reply-To: <1233177944.22831.10.camel@rc-desk>
[-- Attachment #1: Type: text/plain, Size: 925 bytes --]
On Wed, 2009-01-28 at 13:25 -0800, reinette chatre wrote:
> On Wed, 2009-01-28 at 11:05 -0800, Johannes Berg wrote:
> > On Wed, 2009-01-28 at 09:38 -0800, Reinette Chatre wrote:
> > > Cleans uCode key table bit map iwl_clear_stations_table
> > > since all stations are cleared also the key table must be.
> > >
> > > Since the keys are not removed properly on suspend by mac80211
> > > this may result in exhausting key table on resume leading
> > > to memory corruption during removal
> >
> > Just FYI, this is fixed now in mac80211.
>
> Sorry - I missed this. Could you please point me to the patch?
> The problem was encountered in 2.6.29-rc2 (see
> http://bugzilla.kernel.org/show_bug.cgi?id=12415 ) and I would like to
> know if this patch you refer to is included there. If so then we have
> another issue.
Sorry, my mistake, the patch to fix mac80211 suspend/resume is in
for .30.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-01-28 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-28 17:38 [PATCH v2.6.29] iwlwifi: clean key table in iwl_clear_stations_table Reinette Chatre
2009-01-28 19:05 ` Johannes Berg
2009-01-28 21:25 ` reinette chatre
2009-01-28 21:35 ` Johannes Berg [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=1233178554.16048.50.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=reinette.chatre@intel.com \
--cc=tomas.winkler@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