All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stanislaw Gruszka <sgruszka@redhat.com>
To: "Tomáš Janoušek" <tomi@nomi.cz>
Cc: wwguy <wey-yi.w.guy@intel.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Johannes Berg <johannes@sipsolutions.net>,
	security@kernel.org
Subject: Re: iwlagn: memory corruption with WPA enterprise
Date: Mon, 5 Mar 2012 15:57:01 +0100	[thread overview]
Message-ID: <20120305145700.GA17800@redhat.com> (raw)
In-Reply-To: <20120305140130.GA15186@nomi.cz>

On Mon, Mar 05, 2012 at 03:01:30PM +0100, Tomáš Janoušek wrote:
> > That make sense! Your "CPU instructions break things" theory sounds crazy,
> > but I think it's logical. WPA enterprise differ from WPA-PSA (pre shared
> > key) that the key changed periodically, SSL is used when keys are changed
> > (via wpa_supplicant). So looks like 32-bit openssl generate object code
> > that trigger bug on CPU, which crash other processes.
> 
> It seems that someone beat me to it. Since Linus fixed the FPU leaks in
> 3.3-rc4, I haven't experienced the problem. And I was this close! :-)

Yeh, that was really nasty bug. 

> Anyway, thanks for assistance and sorry for being so slow to respond.

No problem. Can you remind me, is this reproducible on 64-bit kernel
with 32-bit user space? I'm asking because I would like to know if we
need to  backport those fixes to our kernel. We do not enable
CONFIG_CRYPTO_AES_NI_INTEL on 32 bit kernel, only on 64 bit, but if this
problem happen with 32-bit user land with 64 bit kernel, we will need to
do backport.

Thanks
Stanislaw

  reply	other threads:[~2012-03-05 14:57 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-29 17:15 iwlagn: memory corruption with WPA enterprise Tomáš Janoušek
2011-10-31 16:03 ` Stanislaw Gruszka
2011-11-09 15:54   ` Tomáš Janoušek
2011-11-09 15:59     ` wwguy
2011-11-09 16:51     ` Stanislaw Gruszka
2011-11-10  9:18       ` Tomáš Janoušek
2011-11-10 11:47         ` Stanislaw Gruszka
2011-11-10 12:53           ` Tomáš Janoušek
2011-11-10 16:07             ` Stanislaw Gruszka
2011-11-10 15:24               ` Guy, Wey-Yi
2011-11-10 16:42                 ` Tomáš Janoušek
2011-11-10 17:02                   ` Larry Finger
2011-11-10 16:30               ` Tomáš Janoušek
2011-11-11  5:47                 ` Stanislaw Gruszka
2011-11-11 15:01                   ` Tomáš Janoušek
2011-11-14 14:07                     ` Stanislaw Gruszka
2011-11-19 18:11                       ` Tomáš Janoušek
2011-11-20  2:13                         ` wwguy
2011-11-20  3:20                           ` Tomáš Janoušek
2011-11-20  4:28                             ` wwguy
2011-11-20 20:40                               ` Tomáš Janoušek
2012-02-10 18:09                                 ` Tomáš Janoušek
2012-02-13  9:25                                   ` Stanislaw Gruszka
2012-02-13 13:09                                     ` Stanislaw Gruszka
2012-02-13 13:29                                       ` Tomáš Janoušek
2012-02-14  9:20                                   ` Stanislaw Gruszka
2012-03-05 14:01                                     ` Tomáš Janoušek
2012-03-05 14:57                                       ` Stanislaw Gruszka [this message]
2012-03-05 15:00                                         ` Tomáš Janoušek
2012-03-05 15:11                                           ` Stanislaw Gruszka
2012-03-05 15:18                                             ` Tomáš Janoušek
2011-11-21 13:05                         ` Stanislaw Gruszka
2011-11-21 13:09                           ` Tomáš Janoušek
2011-11-21 13:40                             ` Stanislaw Gruszka
2011-11-21 14:32                               ` Tomáš Janoušek
2011-11-10 19:31         ` Adrian Chadd
2011-11-11  5:44           ` Stanislaw Gruszka

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=20120305145700.GA17800@redhat.com \
    --to=sgruszka@redhat.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=security@kernel.org \
    --cc=tomi@nomi.cz \
    --cc=wey-yi.w.guy@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.