From: Antonio Quartulli <antonio@open-mesh.com>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] GTK/PTK problem - key.c magic-bitshift
Date: Mon, 18 Nov 2013 22:51:27 +0100 [thread overview]
Message-ID: <20131118215127.GC1443@open-mesh.com> (raw)
In-Reply-To: <CAJ-Vmo=vnP0ch=U+WusC0J5edWS6mzEShWtsWFo1s9x1BBB3aA@mail.gmail.com>
On Mon, Nov 18, 2013 at 01:29:14PM -0800, Adrian Chadd wrote:
> There's a chip bug that's been (as far as I could tell whilst I was at
> QCA) around forever.
>
Do you know if this bug is triggered during write operations to other slots
only (in my case it seems the cache was getting corrupted after a GTK upload)
or if this can happen at any time?
In the first case I could check the cache for possible corruptions only when
ath_key_config() is invoked (I could compare the cache state before the upload
with what I have after it - as Jouni suggested) and call the "resync task" only
in that case.
Cheers,
--
Antonio Quartulli
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
Url : http://lists.ath9k.org/pipermail/ath9k-devel/attachments/20131118/85d9feb7/attachment.pgp
next prev parent reply other threads:[~2013-11-18 21:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 11:08 [ath9k-devel] GTK/PTK problem - key.c magic-bitshift Antonio Quartulli
2013-11-18 21:29 ` Adrian Chadd
2013-11-18 21:44 ` Antonio Quartulli
2013-11-18 21:51 ` Antonio Quartulli [this message]
2013-11-20 8:41 ` Adrian Chadd
2013-11-22 9:18 ` Antonio Quartulli
2013-11-22 9:42 ` Adrian Chadd
2013-11-27 6:48 ` Antonio Quartulli
2013-12-04 13:23 ` [ath9k-devel] Key Cache corruption (was: GTK/PTK problem - key.c magic-bitshift) Antonio Quartulli
2013-12-04 17:08 ` Adrian Chadd
2013-12-09 10:17 ` [ath9k-devel] Key Cache corruption Antonio Quartulli
2013-12-09 19:38 ` Adrian Chadd
2013-12-12 9:17 ` Antonio Quartulli
2013-12-13 12:35 ` Adrian Chadd
2013-12-13 12:55 ` Antonio Quartulli
2014-01-07 15:23 ` Antonio Quartulli
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=20131118215127.GC1443@open-mesh.com \
--to=antonio@open-mesh.com \
--cc=ath9k-devel@lists.ath9k.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