public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: jon <jon@jonshouse.co.uk>
Cc: Valdis.Kletnieks@vt.edu, coreutils@gnu.org, linux-kernel@vger.kernel.org
Subject: Re: Feature request, "create on mount" to create mount point directory on mount, implied remove on unmount
Date: Sun, 5 Jul 2015 15:29:36 +0100	[thread overview]
Message-ID: <20150705142936.GW17109@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1436050108.6501.509.camel@jonspc>

On Sat, Jul 04, 2015 at 11:48:28PM +0100, jon wrote:

> Yes, but like I say automount is normally based on an event. I am simply
> talking about a flag/switch that can be used for optional implied
> mkdir,rmdir around calls to mount() unount() - nothing more, nothing
> less !

umount(2) is not the only way for mount to detached from a mountpoint.
There's exit(2) as well - when the last process in a namespace exits, it
gets dissolved.  What should happen upon those?  Even more interesting question
is what should happen if you do such mount, then clone a process into a new
namespace and have it exit.  Should _that_ rmdir the hell out of that
mountpoint (presumably detaching everything mounted on it in all namespaces)?

What should happen when a process in new namespace decides to unmount that
thing, because they don't what it visible.  Should that take out the instance
in parent namespace? `

  reply	other threads:[~2015-07-05 14:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 12:01 Feature request, "create on mount" to create mount point directory on mount, implied remove on unmount jon
2015-07-04 20:56 ` Valdis.Kletnieks
2015-07-04 22:48   ` jon
2015-07-05 14:29     ` Al Viro [this message]
2015-07-05 15:46       ` jon
2015-07-05 17:39         ` Al Viro
2015-07-05 23:35           ` jon
2015-07-06  1:08             ` Al Viro
2015-07-06  2:34               ` jon
2015-07-06  3:07                 ` Al Viro
2015-07-06  5:40                 ` Valdis.Kletnieks
2015-07-15 14:38     ` Karel Zak

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=20150705142936.GW17109@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=Valdis.Kletnieks@vt.edu \
    --cc=coreutils@gnu.org \
    --cc=jon@jonshouse.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox