[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1329963683.2244.19.camel@perseus.themaw.net>
Date: Thu, 23 Feb 2012 10:21:23 +0800
From: Ian Kent <raven@...maw.net>
To: Thomas Meyer <thomas@...3r.de>
Cc: David Miller <davem@...emloft.net>, linux-kernel@...r.kernel.org,
"H. Peter Anvin" <hpa@...or.com>, autofs@...r.kernel.org,
Linus Torvalds <torvalds@...ux-foundation.org>,
Al Viro <viro@...iv.linux.org.uk>
Subject: Re: compat: autofs v5 packet size ambiguity - update
On Thu, 2012-02-23 at 09:54 +0800, Ian Kent wrote:
> On Thu, 2012-02-23 at 09:48 +0800, Ian Kent wrote:
> > On Wed, 2012-02-22 at 08:12 -0800, Linus Torvalds wrote:
> > > On Wed, Feb 22, 2012 at 1:32 AM, Ian Kent <raven@...maw.net> wrote:
> > > >
> > > > Oh, DOH ...
> > > >
> > > > The process mounting the autofs mount is passing the pipe it will use
> > > > for communication via a mount option so we can do this right in
> > > > fill_super.
> > >
> > > No, we really cannot.
> >
> > Sorry, I think your wrong this time.
>
> On second thought, I suppose other user space users don't "have" to use
> mount(2) ....
Thomas, what does systemd use to mount the autofs mounts that it uses?
>
> >
> > >
> > > The autofs "mount" is done by fork + execve("mount").
> >
> > It's done like this when mounting things inside an already mounted
> > indirect autofs mount or when mounting things on autofs direct mount
> > triggers but, in version 5, mount(2) has always used to mount autofs
> > file systems.
> >
> > Ian
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists