Messages in this thread | | | Date | Mon, 5 Mar 2012 16:11:41 +0100 | From | Stanislaw Gruszka <> | Subject | Re: iwlagn: memory corruption with WPA enterprise |
| |
Hello.
On Mon, Mar 05, 2012 at 04:00:31PM +0100, Tomáš Janoušek wrote: > On Mon, Mar 05, 2012 at 03:57:01PM +0100, Stanislaw Gruszka wrote: > > 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. > > It happens in 32-bit KVM guests on a 64-bit host, so I guess you need it.
Perhaps bug was triggered because KVM 32-bit guest had CONFIG_CRYPTO_AES_NI_INTEL enabled ?
Stanislaw -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |