All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukas Kolbe <lukas@einfachkaffee.de>
To: Ian Kent <raven@themaw.net>
Cc: autofs@linux.kernel.org
Subject: Re: Kernel patch to better support bind-mounts
Date: Tue, 08 Jan 2008 15:41:51 +0100	[thread overview]
Message-ID: <1199803311.27093.5.camel@srss> (raw)
In-Reply-To: <1199798508.3155.48.camel@raven.themaw.net>

Hi Ian!

> Sure, but you'll need to give me a while to re-familiarize myself with
> the history and think about it for a while.

Of course. This patch was sitting here since before christmas and I only
now came around actually talking about it, so no stress with that :)

> > eclipse-3.1 \
> >   /bin          -rw,nosuid,grpid          fileserver:/volumes/vol1/eclipse-3.1/bin.linx86
> > eclipse \
> >   /bin          -rw,nosuid,grpid          :/vol/eclipse-3.1/bin
> 
> Mounts for these multiple offsets are triggered in the same way as
> direct mounts, they are triggered when autofs4_follow_link is called by
> the VFS.
> 
> > 
> > Accessing /vol/eclipse/bin now works flawlessly. But given this map:
> > 
> > jdk-1.5.13 -rw,nosuid,grpid fileserver:/export/stud/vol/jdk-1.5.13/linx86
> > jdk-1.5    -rw,nosuid,grpid :/vol/jdk-1.5.13
> 
> But these are indirect mounts and they are triggered by calling either
> autofs4_lookup or autofs4_revalidate and then indirectly
> try_to_fill_dentry, which is where you added the change I think.

Ok, thanks, then I understand a bit better what's actually happening
there.

> What kernel version is this patch against?

I tested it (IIRC) against 2.6.18 (from debian) and 2.6.23 (from
kernel.org git) - autofs-code doesn't seem to have changed much.

> Ian


-- 
Lukas

  reply	other threads:[~2008-01-08 14:41 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 [this message]
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
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=1199803311.27093.5.camel@srss \
    --to=lukas@einfachkaffee.de \
    --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.