On Fri, Jul 06, 2007 at 09:49:16PM -0400, C. Scott Ananian wrote:
> So, 'dev->bid_type' is garbage when blkid_verify is called, and that's
> causing an infinite loop. It is supposed to be NULL if we don't know
> what the requested block device type is (the original command was
> 'sudo mount -o loop,offset=31744 xo-initrd-test.img
> xo-initrd-test-mnt' ie, there was no -t option given). Setting
> dev->bid_type to NULL allows the mount to complete 'normally' -- it
> gives:
The real question is why was bid->bid_type garbage in the first place?
bid_type is set from /etc/blkid.tab, not from the mount -t option. We
can paper over the bug by explicitly clearing dev->bid_type before we
jump to try_again, but when we cleared all of the tags in while
blkid_tag_next.. blk_set_tag(dev, type, 0,0) loop, that should have
cleared dev->bid_type. Whether or not dev->bid_type was garbage the
first time into blkid_verify() is the big question.
If you can replicate the bug, can you su to root, export
BLKID_DEBUG=0xfffff, and then run the mount command so we can see the
blkid debugging information?
- Ted
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
