search

therealromster / cryptsetup

Automatically exported from code.google.com/p/cryptsetup
GNU General Public License v2.0
0 stars 0 forks source link

Cryptsetup & udev problems if hotplug set #170

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Copied from https://bugzilla.redhat.com/show_bug.cgi?id=984078

Maybe it is libcryptsetup misusing devicemapper somehow. These steps 
demonstrate that dmsetup is at least capable of correct operation, while 
cryptsetup is affected by the problem:

1. Boot F18 with a standard Fedora kernel, login as root.
2. Introduce a similar breakage that udo had in the custom kernel:
   echo '/some/nonexistent/path' > /proc/sys/kernel/hotplug
3. Let there be a block device for testing:
   dd if=/dev/zero of=/nothing bs=1M count=10
   losetup /dev/loop0 /nothing
4. Have cryptsetup create a mapping:
   cryptsetup open --type plain /dev/loop0 test
   (Any random password will do when asked.)
5. And have dmsetup create one too:
   dmsetup create test2 --table '0 1000 zero'
6. See what happened:
   ls -l /dev/mapper

For me it shows 'test' is a block device (incorrectly) and 'test2' is a symlink 
(correctly).

Original issue reported on code.google.com by gmazyl...@gmail.com on 14 Jul 2013 at 10:12

GoogleCodeExporter commented 9 years ago 
I cannot reproduce it reliably and it is really just problem of kernel hotplug 
misconfiguration. 

btw the proper bug is https://bugzilla.redhat.com/show_bug.cgi?id=759402 ...

Original comment by gmazyl...@gmail.com on 23 Jul 2013 at 8:41