cryptmount crashed with SIGSEGV in strlen()

[medic]

Binary package hint: cryptmount

it just didn't mount .. trying again worked ...

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Mon Oct 12 08:31:17 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/cryptmount
NonfreeKernelModules: nvidia
Package: cryptmount 4.0-1
ProcCmdline: /usr/bin/cryptmount --mount crypted
ProcEnviron: PATH=(custom, no user)
ProcVersionSignature: Ubuntu 2.6.31-14.46-generic
SegvAnalysis:
 Segfault happened at: 0x7f683d8563c1 <strlen+17>: movdqa (%rdi),%xmm0
 PC (0x7f683d8563c1) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm0" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: cryptmount
StacktraceTop:
 strlen () from /lib/libc.so.6
 ?? () from /usr/lib/cryptmount/cm-luks.so
 ?? ()
 ?? ()
 ?? ()
Title: cryptmount crashed with SIGSEGV in strlen()
Uname: Linux 2.6.31-14-generic x86_64
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:strlen () at ../sysdeps/x86_64/strlen.S:31
kmluks_get_key (boundtgt=0x20a35b0,
cm_get_key (boundtgt=0x20a35b0,
do_devsetup (pw_ctxt=<value optimized out>,
execute_list (mode=M_MOUNT,

[RW Penney (rwpenney)]

Thanks for finding this bug, and for the helpful stack traces.
I believe this problem is due to differences in the error-checking applied in the LUKS key-manager from other cryptmount key-managers.
I've attached a patch which I hope will sort out the problem.
This patch will be incorporated in future official releases of cryptmount.

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here.

Thanks too for the patch, it should help resolving this issue.

Thanks for taking the time to make Ubuntu better!

[RW Penney (rwpenney)]

The upstream release of cryptmount-4.1 (http://www.sourceforge.net/projects/cryptmount) includes this patch.
cryptmount-4.1-2 is now available in debian-testing, and is scheduled for inclusion in the Maverick Meerkat release of Ubuntu.
cryptmount-4.0.2 has been available in Lucid Lynx for a while, and also includes this patch.

I'd suggest this bug can now be marked as 'resolved'.

[Scott Howard (showard314)]

Thanks for the patch and testing! Marking as fixed released since Ubuntu has had this fixed in Lucid, and Maverick has version 4.1.