From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: compat: autofs v5 packet size ambiguity - update Date: Wed, 22 Feb 2012 07:13:48 -0800 Message-ID: <4F45062C.8000104@zytor.com> References: <20120221.221609.218135609185671883.davem@davemloft.net> <1329889428.2193.45.camel@perseus.themaw.net> <1329890027.2193.48.camel@perseus.themaw.net> <1329890251.2193.50.camel@perseus.themaw.net> <1329903139.2193.66.camel@perseus.themaw.net> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1329903139.2193.66.camel@perseus.themaw.net> Sender: linux-kernel-owner@vger.kernel.org List-ID: Content-Type: text/plain; charset="us-ascii" To: Ian Kent Cc: Linus Torvalds , David Miller , linux-kernel@vger.kernel.org, autofs@vger.kernel.org, Thomas Meyer , Al Viro On 02/22/2012 01:32 AM, Ian Kent 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. > Does that mean that the autofs v5 daemon calls mount() by itself, unlike the older autofs daemon? Otherwise you're reading the compatness of /bin/mount... -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.