Testing of filesystem identification code (blkid/vol_id)

Kees Cook kees.cook at canonical.com
Tue Mar 24 19:52:16 GMT 2009


On Tue, Mar 24, 2009 at 05:39:00PM +0000, Scott James Remnant wrote:
> I'd appreciate some testing of the following packages in my PPA:
> 	deb http://ppa.launchpad.net/scott/ppa/ubuntu jaunty main
> 	deb-src http://ppa.launchpad.net/scott/ppa/ubuntu jaunty main

> Along with the updates to util-linux, my PPA contains updates to udev,
> dmsetup and mdadm that change the rules to run "blkid" instead of
> "vol_id".

I gave this a shot, and it was bad news for my configuration (LVM
root on RAID1 on SATA).  It seems that blkid hung, (each of the
about 12? 16? instances) spinning at 100% CPU, and never brought up
the md devices.  Once I brought them up manually, LVM was activated
without a hitch.  Due to the hung blkids, I assume udevsettle failed
to ever finish, so my system hung again at "loading hardware drivers".
After getting past that[1], I manually mounted everything, killed the
blkids, and downgraded to stock jaunty again for now.  :)


[1] I hit ctrl-alt-del, and that seemed to continue the boot, rather than
rebooting... is that expected behavior from upstart?

Kees Cook
Ubuntu Security Team

More information about the ubuntu-devel mailing list