From: Torben Viets <viets@web.de>
To: linux-kernel@vger.kernel.org
Subject: LRW/XTS + Via Padlock Bug in 2.6.24-rc7?
Date: Wed, 09 Jan 2008 01:12:02 +0100 [thread overview]
Message-ID: <47841152.8080705@web.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 2489 bytes --]
Hello,
I have a Via Epia Sn1000 Board with a padlock-aes crypto accelerator, if
I uses this with cryptsetup and LRW or XTS, I get a kernel panic and
cryptsetup never ends.
XTS:
cryptsetup -c aes-xts-plain -s 256 luksFormat /dev/raid/test
general protection fault: 0000 [#1]
Modules linked in: lrw padlock_aes xts xt_TCPMSS xt_tcpmss
iptable_mangle pppoe pppox ipt_MASQUERADE xt_tcpudp iptable_nat nf_nat
nf_conntrack_ipv4 iptable_filter ip_tables x_tables af_packet
ppp_generic slhc aes_i586 dm_crypt dm_mod
Pid: 5991, comm: kcryptd Not tainted (2.6.24-rc7 #4)
EIP: 0060:[<f88cf028>] EFLAGS: 00010296 CPU: 0
EIP is at aes_crypt_copy+0x28/0x40 [padlock_aes]
EAX: f6385ff0 EBX: f61ce450 ECX: 00000001 EDX: f61ce430
ESI: f6235dac EDI: f6385ff0 EBP: f6235e00 ESP: f6235dac
DS: 007b ES: 007b FS: 0000 GS: 0000 SS: 0068
Process kcryptd (pid: 5991, ti=f6234000 task=f63fcab0 task.ti=f6234000)
Stack: 811cd642 f3a4d1ea d12d0cfa 3098ed1e 00000000 ffffff24 c02695d8
00000060
f61ce450 f6385ff0 f6385ff0 f88cf096 f61ce430 f6385ff0 f6385ff0
00000010
f88c90fc f581f3e0 f6235e34 f6235ea8 00000010 f89b59df c29b34ff
391d88f0
Call Trace:
[<c02695d8>] gf128mul_x_ble+0x68/0x90
[<f88cf096>] aes_decrypt+0x56/0x60 [padlock_aes]
[<f88c90fc>] crypt+0xdc/0x110 [xts]
[<f88cf040>] aes_decrypt+0x0/0x60 [padlock_aes]
[<f88c9222>] decrypt+0x42/0x50 [xts]
[<f88cf810>] aes_encrypt+0x0/0x60 [padlock_aes]
[<f88cf040>] aes_decrypt+0x0/0x60 [padlock_aes]
[<f886a7de>] crypt_convert_scatterlist+0x6e/0xe0 [dm_crypt]
[<f886a9ea>] crypt_convert+0x19a/0x1c0 [dm_crypt]
[<f886aa10>] kcryptd_do_crypt+0x0/0x260 [dm_crypt]
[<f886aa59>] kcryptd_do_crypt+0x49/0x260 [dm_crypt]
[<c01195c0>] update_curr+0x70/0x110
[<f886aa10>] kcryptd_do_crypt+0x0/0x260 [dm_crypt]
[<c012b116>] run_workqueue+0x66/0xe0
[<c03f5279>] schedule+0x149/0x270
[<c012b8f0>] worker_thread+0x0/0x100
[<c012b98d>] worker_thread+0x9d/0x100
[<c012e790>] autoremove_wake_function+0x0/0x50
[<c012b8f0>] worker_thread+0x0/0x100
[<c012e452>] kthread+0x42/0x70
[<c012e410>] kthread+0x0/0x70
[<c0104acf>] kernel_thread_helper+0x7/0x18
=======================
Code: <f3> 0f a7 c8 8b 5c 24 20 8b 74 24 24 8b 7c 24 28 83 c4 2c c3 8d 74
EIP: [<f88cf028>] aes_crypt_copy+0x28/0x40 [padlock_aes] SS:ESP
0068:f6235dac
---[ end trace 9ae4eb03d4e4c477 ]---
note: kcryptd[5991] exited with preempt_count 1
I'm not on the lklm, so please CC me.
I hope you have enough information.
Thank you and greetings
Torben Viets
[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 10610 bytes --]
next reply other threads:[~2008-01-09 0:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-09 0:12 Torben Viets [this message]
2008-01-09 22:55 ` LRW/XTS + Via Padlock Bug in 2.6.24-rc7? Torben Viets
2008-01-10 3:03 ` Herbert Xu
-- strict thread matches above, loose matches on Subject: below --
2008-01-10 10:43 Torben Viets
2008-01-10 20:48 ` Herbert Xu
2008-01-10 23:21 ` Torben Viets
2008-01-10 23:58 ` Herbert Xu
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=47841152.8080705@web.de \
--to=viets@web.de \
--cc=linux-kernel@vger.kernel.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 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.