Messages in this thread | | | Date | Wed, 30 Jan 2008 15:42:04 +0100 | From | Karel Zak <> | Subject | Re: [patch 01/26] mount options: add documentation |
| |
On Wed, Jan 30, 2008 at 10:09:03AM +0100, Miklos Szeredi wrote: > > - loop: how is the connection between file and loop device maintained? > > We also discussed this with Karel, maybe it didn't make it onto lkml. > > The proposed solution was to store the "loop" flag separately in a > file under /var. It could just be an empty file for each such loop > device: > > /var/lib/mount/loops/loop0 > > This file is created by mount(8) if the '-oloop' option is given. And > umount(8) automatically tears down the loop device if it finds this > file.
It seems we needn't this solution. There is loop auto-destruction patch in -mm.
Kernel part: http://marc.info/?l=linux-kernel&m=119361296818388&w=2
mount(8) part: http://marc.info/?l=util-linux-ng&m=119362955431694&w=2
So, with this patch mount(8) needn't to maintain info about loops and umount(8) doesn't need to call LOOP_CLR_FD ioctl, because umount(2) is enough.
Karel
-- Karel Zak <kzak@redhat.com>
| |