Hi Kim, Thanks massively for your clear recipe to reproduce this crash, it's been really helpful.
On Sun, Mar 01, 2015 at 04:37:00PM +0100, Kim Christensen wrote: > >Here's the steps to trigger partman segfault: > >1. Create ext2 partition on /dev/md0, set mountpoint /boot >2. Create crypt partitions on /dev/md1, /dev/md2, /dev/sdc5 >3. Configure crypt partitions > - Using passphrase on /dev/md1 and /dev/md2 > - Using random key on /dev/sdc5 >4. Configure swap space on cryptdisk for /dev/sdc5 >5. Create LVM space on cryptdisks for /dev/md1 and /dev/md2 >6. Configure LVM, create two separate VGs (one on each cryptdisk) >7. Configure LVM, create LVs for each VG >8. Finish LVM >9. Disk detection triggered, stuck at 81% and segfault > >Been trying for about ten times now and always get the above result. I can repeat the same problem here with a similar recipe in a VM with two virtual disks, but the exactl details don't really matter so much there. What is important is that I've managed to get a core dump out from my parted_server crash, and I can see: Core was generated by `parted_server'. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x000000000040b4b1 in command_get_file_system () at parted_server.c:1802 1802 if (0 == strncmp(part->fs_type->name, "linux-swap", 10)) (gdb) bt #0 0x000000000040b4b1 in command_get_file_system () at parted_server.c:1802 #1 0x000000000040eef2 in main_loop () at parted_server.c:2431 #2 0x0000000000402bf0 in main (argc=<optimized out>, argv=<optimized out>) at parted_server.c:2522 (gdb) p part->fs_type $1 = (const PedFileSystemType *) 0x0 which is an obvious crash. Digging further... -- Steve McIntyre, Cambridge, UK. st...@einval.com "I've only once written 'SQL is my bitch' in a comment. But that code is in use on a military site..." -- Simon Booth -- To UNSUBSCRIBE, email to debian-boot-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/20150302043551.gt6...@einval.com
