diff options
author | Dave Reisner <dreisner@archlinux.org> | 2012-11-24 16:37:29 +0100 |
---|---|---|
committer | Dave Reisner <dreisner@archlinux.org> | 2012-11-26 02:08:57 +0100 |
commit | b9d81a088ad0aa694b335118cf4ee70ad3ad1712 (patch) | |
tree | 33cd5a4d3b329e6b6da48a08c0ea8d1b055221a3 /01-memdisk.rules | |
parent | d64243de39f6d76edf8150b1d81d586345758fed (diff) | |
download | mkinitcpio-b9d81a088ad0aa694b335118cf4ee70ad3ad1712.tar.gz mkinitcpio-b9d81a088ad0aa694b335118cf4ee70ad3ad1712.tar.xz |
shutdown: teardown loop devices only after umount
This still isn't really ideal, but attempting to detach loops while
they're still mounted will definitely fail. Ideally, the loop device is
in autoclear mode and dropping its refcount to 0 on umount will cause
the backing file to be detached from the loop.
Of course, this all gets way too complicated for userspace to handle
when dealing with the sort of rat's nest of loop devices that ArchISO
sets up. The kernel doesn't help us out here by populating things like
holders/ and slaves/, but I'm not sure it could.
Maybe there's a better way...
Signed-off-by: Dave Reisner <dreisner@archlinux.org>
Diffstat (limited to '01-memdisk.rules')
0 files changed, 0 insertions, 0 deletions