From: Johannes Berg <johannes@sipsolutions.net>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: mac80211: Breakage in software encryption (iwl3945)
Date: Sun, 24 Jan 2010 11:56:53 +0100 [thread overview]
Message-ID: <1264330613.23766.17.camel@johannes.local> (raw)
In-Reply-To: <1264277460.13250.10.camel@maxim-laptop>
[-- Attachment #1: Type: text/plain, Size: 997 bytes --]
Maxim,
Your mail is confusing me.
On Sat, 2010-01-23 at 22:10 +0200, Maxim Levitsky wrote:
> I updated the kernel and lost connection to my WPA2
> AP. Strangely the WPA handshake completes, but DHCP not.
What did you upgrade to?
> I also unfortunately found that all that time I was using software
> encryption (this is iwl3945 loaded with swcrypto=1).
> Hardware encryption doesn't work ether and didn't work in the slightly
> older kernel (but it did work once, I sure)
That must be a different problem, surely?
> Now, the commit a6bae9e7ab19876a157c91019852395539e4f20e breaks software
> encryption, with behaviour like described above.
And how did you arrive at that conclusion? Have you reverted the patch
and it works again? I really don't see how this particular patch could
break it since afaict it's entirely correct, there are exactly two tests
for IEEE80211_TX_INTFL_DONT_ENCRYPT in mac80211, both of which execute
before the code I removed.
johannes
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2010-01-24 10:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-23 20:10 mac80211: Breakage in software encryption (iwl3945) Maxim Levitsky
2010-01-24 10:32 ` Marcus Better
2010-01-24 11:15 ` Marcus Better
2010-01-24 10:40 ` Sedat Dilek
2010-01-24 10:56 ` Johannes Berg [this message]
2010-01-24 18:24 ` Maxim Levitsky
2010-01-24 23:27 ` Jochen Friedrich
2010-01-25 0:05 ` Jochen Friedrich
2010-01-25 9:32 ` Johannes Berg
2010-01-25 15:10 ` Maxim Levitsky
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=1264330613.23766.17.camel@johannes.local \
--to=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=maximlevitsky@gmail.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