Hello,
On Fri, Aug 21, 2009 at 9:01 AM, martin f krafft<[email protected]> wrote:
> If pumount is told to be --lazy on a crypto-volume, it essentially
> calls /sbin/umount -l, but then immediately runs luks_release, which
> will fail:
>
> % sudo cryptsetup -d $HOME/keys/backup/backupdisk.key luksOpen /dev/sdc
> _dev_sdc
> key slot 0 unlocked.
> Command successful.
> % sudo mount /dev/mapper/_dev_sdc /mnt
> % (cd /mnt && sleep 300) &
> % sudo umount /mnt
> umount: /mnt: device is busy.
> (In some cases useful info about processes that use
> the device is found by lsof(8) or fuser(1))
> % sudo umount -l /mnt
> % sudo cryptsetup luksClose /dev/mapper/_dev_sdc
> Command failed: Device busy
> [waiting…]
> [1] + done (; cd /mnt && sleep 300; )
> % sudo cryptsetup luksClose /dev/mapper/_dev_sdc
> %
>
> Either pumount should not offer --lazy for crypto-volumes, or it
> should spawn a process (or some other means) to release the
> crypto-volume as soon as the device has actually been unmounted.
That's a very good point. I think I'll disable that for crypto
volumes and issue a warning for other volumes, as, in fact, a lazy
umount for removable devices is the best way to shoot oneself in the
foot !
Thanks for pointing the problem !
Vincent, who hasn't done much work on pmount for a while, and
will not for another while (just look at -private tomorrow).
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
