Comment # 3 on bug 1140564 from Michael Hirmke

Hi,

(In reply to Coly Li from comment #2)
> Hi Michael,
> 
> Let me handle this issue. Since I never use luks device before, could you
> please give me some hint, then I may try to reproduce and debug.

just a notice: I'm not a developer, especially not a kernel or driver
developer, so bear with me - I might not be able to answer all of your
questions.

> 
> 1) What is the kernel driver os the luks device? I assume it is
> drivers/md/dm-crypt.c, is there anything more involved too?

I can't provide more information than you can see from the kernel backtrace.
I am not sure, what modules might be involved besides the ones mentioned there.

> 2) Could you please to offer me a procedure on how to reproduce the oops, it
> will safe me a lot of time on learning how to use luks device.

I do nothing more than running "cryptsetup open/close".

/sbin/cryptsetup open --type luks \
                   --key-file "$_keyfile" \
                   --batch-mode \
                   --verbose \
                   /dev/sdg1 \
                   /dev/mapper/backup_dup_secure
...
/sbin/cryptsetup close --type luks \
                    --batch-mode \
                    --verbose \
                    /dev/mapper/backup_dup_secure


> 
> Thanks.
> 
> Coly Li

Bye.
Michael.