From owner-freebsd-fs@FreeBSD.ORG  Tue May 12 07:46:07 2015
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 134724EA
 for <freebsd-fs@freebsd.org>; Tue, 12 May 2015 07:46:07 +0000 (UTC)
Received: from mail-wi0-x22d.google.com (mail-wi0-x22d.google.com
 [IPv6:2a00:1450:400c:c05::22d])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 9B56715A8
 for <freebsd-fs@freebsd.org>; Tue, 12 May 2015 07:46:06 +0000 (UTC)
Received: by wizk4 with SMTP id k4so139858545wiz.1
 for <freebsd-fs@freebsd.org>; Tue, 12 May 2015 00:46:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=sender:date:from:to:cc:subject:message-id:mail-followup-to
 :references:mime-version:content-type:content-disposition
 :in-reply-to:user-agent;
 bh=OMWEBC6ReIiFV5Vu6Tewud31Sx0rBQrh4cNxmToJDRk=;
 b=mKbGSox+EIAgoofw/rW/il+bEZGGdTaHv4D3klo8JshOqM1jf5VBdP6vhaePpvElsM
 +1uRqK2V91KCVvaBGZscu5Co7qtL9Rrwgjb6rWb+SsSdMgmAybYTYSCS3/VSUfIXEexA
 wj3Ix2DO1RxGYIVNpvmHDryMLqFAVShErRTN4DYXcYHJkGR50ReY+BmGiLZjcesQ+52X
 Az3INJg5VXIbHbV5D9OgBM0Y62LZHnT5met2QvdYAb2yBGjf2SP5YGzLG04EqnoGvBkJ
 Kk7tqLAd7Xadj1Wx5EsnshfXx/sxNpcYFdhP8gzMSFJ8VoouMbLqfCr66Cug1sOC2bU2
 p6KQ==
X-Received: by 10.180.104.225 with SMTP id gh1mr27032119wib.65.1431416764855; 
 Tue, 12 May 2015 00:46:04 -0700 (PDT)
Received: from brick.home (etm123.neoplus.adsl.tpnet.pl. [83.20.158.123])
 by mx.google.com with ESMTPSA id fv7sm1505638wic.1.2015.05.12.00.46.03
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Tue, 12 May 2015 00:46:03 -0700 (PDT)
Sender: =?UTF-8?Q?Edward_Tomasz_Napiera=C5=82a?= <etnapierala@gmail.com>
Date: Tue, 12 May 2015 09:46:02 +0200
From: Edward Tomasz =?utf-8?Q?Napiera=C5=82a?= <trasz@FreeBSD.org>
To: Rick Macklem <rmacklem@uoguelph.ca>
Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>
Subject: Re: RFC: should automounted file systems be exportable?
Message-ID: <20150512074602.GA93864@brick.home>
Mail-Followup-To: Rick Macklem <rmacklem@uoguelph.ca>,
 FreeBSD Filesystems <freebsd-fs@freebsd.org>
References: <402295202.36197924.1431397070727.JavaMail.root@uoguelph.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <402295202.36197924.1431397070727.JavaMail.root@uoguelph.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 12 May 2015 07:46:07 -0000

On 0511T2217, Rick Macklem wrote:
> A recent bug was reported related to mountd and the
> "automounted" flag.
> 
> Loosely related to this is the question...
> Should automounted file systems be exportable?
> 
> I haven't tested it, but I suspect that it would be
> broken and the NFS server will reply NFSERR_STALE
> after the file system has been dismounted.
> 
> So, should I patch mountd so that it won't export
> automounted file systems?

Exporting an automounted filesystem doesn't seem to make much sense,
I agree, but I'm not sure if adding code to prevent it is such
a good idea.  If the user asks for it, by putting it into exports(5),
it's his fault; the only thing this code could add would be a more
friendly error message.