cryptmount reports segfault in dmesg

Bug #488437 reported by vbargsten
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cryptmount (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: cryptmount

I have a LUKS encrypted data partition and want it to mount it at boot, ideally before fstab. As there are problems with cryptsetup password promt etc with ubuntu 9.10, I tried to use cryptmount instead.

/etc/cryptmount/cmtab content:
data {
      keyformat=luks
      dev=/dev/sda6
      keyfile=/dev/sda6
      dir=/data
      fstype=ext3
      }

In /etc/default/cryptmount, I tried both
CM_EARLYDV="data"
and
CM_BOOTDV="data"
and together.

Problem:
dmesg | grep crypt
[ 14.988099] cryptmount[882]: segfault at 0 ip 00be4f43 sp bfe707cc error 4 in libc-2.10.1.so[b72000+13e000]
[ 16.411724] cryptmount[1143]: segfault at 0 ip 009b5f43 sp bfb3771c error 4 in libc-2.10.1.so[943000+13e000]

Manually starting

sudo /etc/init.d/cryptmount start
[sudo] password for vb:
Starting cryptmount targets (hit shift/ctrl if short of entropy):
Bitte geben Sie das Passwort für das Ziel »data« ein:
sh: /sbin/udevsettle: not found
vb@vbmobil:~$

mounts data successfully. Btw., there seems to be a problem with udevsettle (not available anymore?)

System is Xubuntu 9.10, Kernel 2.6.31-15-generic, cryptmount cryptmount-4.0
I can do further debugging if required, though the problem is the segfault occurs on boot only.

Revision history for this message
Greg Odero-Jowi (ojgreg) wrote :

I rolled back to kernel 2.6.28-16-generic as this allows me to boot, unlock and mount LUKS partitions successfully. All kernel releases since have the same bug.

Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner.

There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test the current Ubuntu development version (10.10). If you can test it, and it is still an issue, we would appreciate if you could upload updated logs by running apport-collect 488437, and any other logs that are relevant for this particular issue.

Changed in cryptmount (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for cryptmount (Ubuntu) because there has been no activity for 60 days.]

Changed in cryptmount (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.