Return-Path: linux-nfs-owner@vger.kernel.org Received: from mx11.netapp.com ([216.240.18.76]:11697 "EHLO mx11.netapp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752664Ab3HBQvc convert rfc822-to-8bit (ORCPT ); Fri, 2 Aug 2013 12:51:32 -0400 From: "Adamson, Dros" To: "J. Bruce Fields" CC: linux-nfs list Subject: Re: SP4_MACH_CRED Date: Fri, 2 Aug 2013 16:51:28 +0000 Message-ID: References: <20130731213904.GB2668@fieldses.org> <75E5568D-320C-45A1-B7E6-23CE73217BAF@netapp.com> <20130731234800.GC2668@fieldses.org> <0E0FF4CB-4388-417B-9D1C-24940472D844@netapp.com> <20130802153215.GK17581@fieldses.org> In-Reply-To: <20130802153215.GK17581@fieldses.org> Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Sender: linux-nfs-owner@vger.kernel.org List-ID: On Aug 2, 2013, at 11:32 AM, J. Bruce Fields wrote: > On Thu, Aug 01, 2013 at 02:03:29PM +0000, Adamson, Dros wrote: >> The other case we are aiming for with the client is to be able to use >> the machine cred in recovery when the user's creds expire so that >> flushing of buffers can happen once recovery is complete. Of course, >> if you don't want to see the flushing changes, this is useless. > > Just so I understand: addressing this case would require allowing more > operations, right? (OPEN to do the reclaim, for example.) Correct. -dros > > --b.