From: Ian Molton <spyro@armlinux.org>
To: linux-kernel@vger.kernel.org
Subject: RFC - named loop devices...
Date: Tue, 21 May 2002 01:55:17 +0100 [thread overview]
Message-ID: <20020521015517.609d5516.spyro@armlinux.org> (raw)
I havent thought about this too much, but...
When /etc/mtab is a symlink to /proc/mounts the umount command will fail
to unmount loopback mounted filesystems properly.
I was wondering if a solution to this would be to introduce 'named'
loopback devices.
with named loop devices, umount will then know that mount was the
creator of a loopback device that it mounted, and can safely destroy it.
at present, mounting and unmounting disc images causes one to run out of
loopback devices rather rapidly.
If I were to knock up a patch to implement named loop devices, would it
stand a chance of being accepted?
also, how should this work? should the name be that of the creating
process or should it just be a field that the creator can fill in as it
pleases?
next reply other threads:[~2002-05-21 0:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-21 0:55 Ian Molton [this message]
2002-05-21 6:05 ` RFC - named loop devices Frank Schaefer
2002-05-21 19:11 ` Denis Vlasenko
2002-05-23 17:01 ` Ian Molton
2002-05-23 17:04 ` Russell King
2002-05-24 23:40 ` jw schultz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020521015517.609d5516.spyro@armlinux.org \
--to=spyro@armlinux.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.