From owner-freebsd-fs@FreeBSD.ORG  Thu Dec 25 10:16:15 2014
Return-Path: <owner-freebsd-fs@FreeBSD.ORG>
Delivered-To: freebsd-fs@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id B1F762FF
 for <freebsd-fs@freebsd.org>; Thu, 25 Dec 2014 10:16:15 +0000 (UTC)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 254393F11
 for <freebsd-fs@freebsd.org>; Thu, 25 Dec 2014 10:16:14 +0000 (UTC)
Received: from tom.home (kostik@localhost [127.0.0.1])
 by kib.kiev.ua (8.14.9/8.14.9) with ESMTP id sBPAG5Om067525
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO);
 Thu, 25 Dec 2014 12:16:05 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
DKIM-Filter: OpenDKIM Filter v2.9.2 kib.kiev.ua sBPAG5Om067525
Received: (from kostik@localhost)
 by tom.home (8.14.9/8.14.9/Submit) id sBPAG46k067524;
 Thu, 25 Dec 2014 12:16:04 +0200 (EET)
 (envelope-from kostikbel@gmail.com)
X-Authentication-Warning: tom.home: kostik set sender to kostikbel@gmail.com
 using -f
Date: Thu, 25 Dec 2014 12:16:04 +0200
From: Konstantin Belousov <kostikbel@gmail.com>
To: Rick Macklem <rmacklem@uoguelph.ca>
Subject: Re: RFC: new NFS mount option to work around Solaris server bug
Message-ID: <20141225101604.GC1754@kib.kiev.ua>
References: <962761800.2101281.1419462898537.JavaMail.root@uoguelph.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <962761800.2101281.1419462898537.JavaMail.root@uoguelph.ca>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-Spam-Status: No, score=-2.0 required=5.0 tests=ALL_TRUSTED,BAYES_00,
 DKIM_ADSP_CUSTOM_MED,FREEMAIL_FROM,NML_ADSP_CUSTOM_MED autolearn=no
 autolearn_force=no version=3.4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on tom.home
Cc: FreeBSD Filesystems <freebsd-fs@freebsd.org>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.18-1
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: Thu, 25 Dec 2014 10:16:15 -0000

On Wed, Dec 24, 2014 at 06:14:58PM -0500, Rick Macklem wrote:
> Hi,
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=193128
> 
> This bug report discusses a bug in the Solaris NFS server
> that is tickled by the way FreeBSD currently does exclusive
> open in the NFS client.
> FreeBSD sets both the mtime to the time of the client and
> also the file's mode using a Setattr RPC done after an
> exclusive create of the file in an exclusive open.
> 
> Jason (jnaughto@ee.ryerson.ca) was able to figure out that
> the server bug can be avoided if the mtime is set to the
> server's time (xxx_TOSERVER option in the Setattr RPC request).
> 
> I'd like to propose a new mount option that forces the
> FreeBSD client to use xxx_TOSERVER for setting times,
> mostly to be used as a work around for this Solaris server bug.
> 1 - Does doing this make sense to others?
> 2 - If the answer to one is "Yes", then what do you think
>     the option should be called?
>     useservertime
>     useservtm
>     ust
>     OR ??

What are drawbacks of unconditionally using the workaround ?