All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Staubach <staubach@redhat.com>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Kernel patch to better support bind-mounts
Date: Wed, 05 Mar 2008 09:19:37 -0500	[thread overview]
Message-ID: <47CEABF9.8090108@redhat.com> (raw)
In-Reply-To: <1204685216.3081.7.camel@raven.themaw.net>

Ian Kent wrote:
> On Tue, 2008-03-04 at 08:25 -0500, Peter Staubach wrote:
>   
>> Lukas Kolbe wrote:
>>     
>>> Hi Ian!
>>>
>>> Ping? :)
>>>
>>> We use this patch now for several servers and clients (debian etch with
>>> 2.6.18, ubuntu feisty with 2.6.20 and some test systems with 2.6.23),
>>> and have seen no regression so far, only working automounts :)
>>> I'd love to see this change upstream, so that I don't have to worry
>>> about constantly patching my own kernel anymore :)
>>>       
>> Why does adding mount on access(2) make things work better?  What works 
>> better?
>>     
>
> Lucas has recursive maps.
> For these mounts to work, we need to ensure that there aren't dependent
> mounts in the mount point path itself before proceeding. We've used the
> access system call, made just prior to performing the mount, to make
> this happen. In this case, however, the lookup flags in the kernel where
> not triggering the mount.

And this does not trigger mounts by other applications, such as ls, too?

    Thanx...

       ps

  reply	other threads:[~2008-03-05 14:19 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-08 10:38 Kernel patch to better support bind-mounts Lukas Kolbe
2008-01-08 13:21 ` Ian Kent
2008-01-08 14:41   ` Lukas Kolbe
2008-01-08 14:50     ` Ian Kent
2008-03-04 12:47 ` Lukas Kolbe
2008-03-04 13:25   ` Peter Staubach
2008-03-05  2:46     ` Ian Kent
2008-03-05 14:19       ` Peter Staubach [this message]
2008-03-05 14:24         ` Lukas Kolbe
2008-03-05 14:29           ` Peter Staubach
2008-03-05  2:47   ` Ian Kent

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=47CEABF9.8090108@redhat.com \
    --to=staubach@redhat.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.net \
    /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.