From: Herbert Xu <herbert@gondor.apana.org.au>
To: timlee@sina.com
Cc: linux-crypto@vger.kernel.org
Subject: Re: Hit OOPS on FPU save and restore while useing AESNI for IPSec on 32 bit System
Date: Sat, 25 Feb 2012 19:37:02 +1100 [thread overview]
Message-ID: <20120225083702.GA19389@gondor.apana.org.au> (raw)
In-Reply-To: <20120223021435.BEE08153400@mail3-79.sinamail.sina.com.cn>
timlee@sina.com wrote:
> Hi All,
>
> Recently I hit an OOPS on FPU save/restore in Linux version 2.6.38.8 using aesni_intel_asm.S and aesni_intel_glue.c for native IPSec(netkey) on 32bit System. The same OOPS were found in versions 2.6.39.4, 3.0.x and 3.1.x.But I did not hit this problem in 64 bit system for all these versions.
>
> My platform information:
> "Linux dnsubuntu 2.6.38.8 #7 SMP Sat Nov 12 03:11:12 CST 2011 i686 i686 i386 GNU/Linux"
Please try the latest git tree (rc4). It should be fixed.
Cheers,
--
Email: Herbert Xu <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
next prev parent reply other threads:[~2012-02-25 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-23 2:14 Hit OOPS on FPU save and restore while useing AESNI for IPSec on 32 bit System timlee
2012-02-25 8:37 ` Herbert Xu [this message]
2012-02-29 12:31 ` Hit OOPS on FPU save and restore while useing AESNI for IPSecon " TimLee
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=20120225083702.GA19389@gondor.apana.org.au \
--to=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=timlee@sina.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