Patch Works. Tested with 2.6.23.11 on Via C7 with aes-lrw-benbi and
key-size 384 bit. Filesystem was an ext3 (default options) on top of
plain partition, Raid-1, and Raid-5.
Thanks a lot,
Alexander
On 26. Dec 2007, at 14:48 Uhr, Herbert Xu wrote:
Please let me know if the following patch
Patch Works. Tested with 2.6.23.11 on Via C7 with aes-lrw-benbi and
key-size 384 bit. Filesystem was an ext3 (default options) on top of
plain partition, Raid-1, and Raid-5.
Thanks a lot,
Alexander
On 26. Dec 2007, at 14:48 Uhr, Herbert Xu wrote:
Please let me know if the following patch
On Sun, Dec 23, 2007 at 06:22:14PM +, Alexander Eichhorn wrote:
>
> BUG: unable to handle kernel paging request at virtual address f800
> printing eip:
> c03bbc8c
> *pde =
> Oops: [#1]
> PREEMPT
> Modules linked in:
> CPU:0
> EIP:0060:[]Not tainted VLI
> EFLAGS:
On Sun, Dec 23, 2007 at 06:22:14PM +, Alexander Eichhorn wrote:
BUG: unable to handle kernel paging request at virtual address f800
printing eip:
c03bbc8c
*pde =
Oops: [#1]
PREEMPT
Modules linked in:
CPU:0
EIP:0060:[c03bbc8c]Not tainted VLI
EFLAGS:
Hi,
while playing around with AES encrypted block devices (in LRW mode)
on top of Software Raid-1/5 volumes I experienced a set of Kernel
OOPSes which seem to be related to the current PadLock-AES driver.
PadLock-AES in LRW mode also failed when layered directly above a raw
disk
Hi,
while playing around with AES encrypted block devices (in LRW mode)
on top of Software Raid-1/5 volumes I experienced a set of Kernel
OOPSes which seem to be related to the current PadLock-AES driver.
PadLock-AES in LRW mode also failed when layered directly above a raw
disk
6 matches
Mail list logo