Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754880Ab2BWB5R (ORCPT ); Wed, 22 Feb 2012 20:57:17 -0500 Received: from mail-pz0-f46.google.com ([209.85.210.46]:48392 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752348Ab2BWB5P (ORCPT ); Wed, 22 Feb 2012 20:57:15 -0500 MIME-Version: 1.0 In-Reply-To: <1329961703.2244.8.camel@perseus.themaw.net> 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> <1329961703.2244.8.camel@perseus.themaw.net> From: Linus Torvalds Date: Wed, 22 Feb 2012 17:56:55 -0800 X-Google-Sender-Auth: w9nkDVzhrhVuiws3fSJeZoJKc4M Message-ID: Subject: Re: compat: autofs v5 packet size ambiguity - update To: Ian Kent Cc: David Miller , linux-kernel@vger.kernel.org, "H. Peter Anvin" , autofs@vger.kernel.org, Thomas Meyer , Al Viro Content-Type: text/plain; charset=ISO-8859-1 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1258 Lines: 34 On Wed, Feb 22, 2012 at 5:48 PM, Ian Kent wrote: > > Sorry, I think your wrong this time. Well, that would be good, actually. Doing the test itself at mount time is certainly the simpler approach. >> 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. Is that true for legacy autofs daemons too that distros ship? Because those are the ones we'd be fighting.. Because when I do git grep '\