linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org, autofs@linux.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [VFS-RFC] autofs4 and bind, rbind and move mount requests
Date: Tue, 24 May 2005 09:06:07 +0800 (WST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0505240846410.26293@wombat.indigo.net.au> (raw)
In-Reply-To: <E1DaG04-0002hk-00@dorka.pomaz.szeredi.hu>

On Mon, 23 May 2005, Miklos Szeredi wrote:

> > Perhaps not in this case.
> 
> Maybe I'm misunderstanding.
> 
> Are you talking about an automounted filesystem, or the autofs
> filesystem itself.

I'm talking about the autofs filesystem (actually the autofs4 module).

> 
> With the later I can well imagine that you have problems with bind and
> move.

yep.

I'm not really concerned about whether bind and move mounts work or not. I 
just need to establish whether these should be supported and if so, how 
they should work so I can resolve the problem. Personally, I would be 
happy to say these types of mounts are not supported by autofs if I could 
veto the requests.

atm I can easily panic the kernel. As I said, it would be fairly easy to 
fail silently but ....

There's not much in it but see:
http://bugme.osdl.org/show_bug.cgi?id=4589

Sorry that my initial post was unclear and perhaps incomplete but mostly 
people are not that familiar with automounting and often they don't really 
want to know about it. I guess they have their own priorities.

Thanks for your interest.
Ian

  reply	other threads:[~2005-05-24  1:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-23 14:34 [VFS-RFC] autofs4 and bind, rbind and move mount requests raven
2005-05-23 15:02 ` Miklos Szeredi
2005-05-23 16:00   ` raven
2005-05-23 16:41     ` Miklos Szeredi
2005-05-24  1:06       ` Ian Kent [this message]
2005-05-24  5:59         ` Miklos Szeredi
2005-05-24 15:24           ` raven
2005-05-24 17:15             ` Miklos Szeredi
2005-05-25  1:19               ` Ian Kent
2005-05-24 16:28 ` Jeff Moyer

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=Pine.LNX.4.58.0505240846410.26293@wombat.indigo.net.au \
    --to=raven@themaw.net \
    --cc=autofs@linux.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    /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;
as well as URLs for NNTP newsgroup(s).