Return-Path: Received: from mail-ig0-f176.google.com ([209.85.213.176]:38166 "EHLO mail-ig0-f176.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932542AbbD0RsU (ORCPT ); Mon, 27 Apr 2015 13:48:20 -0400 Received: by igbhj9 with SMTP id hj9so68694536igb.1 for ; Mon, 27 Apr 2015 10:48:19 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: Date: Mon, 27 Apr 2015 13:48:19 -0400 Message-ID: Subject: Re: [PATCH 1/1] Recover from stateid-type error on SETATTR From: Olga Kornievskaia To: Trond Myklebust , Anna Schumaker Cc: linux-nfs Content-Type: text/plain; charset=UTF-8 Sender: linux-nfs-owner@vger.kernel.org List-ID: Any comments on this patch? On Tue, Apr 21, 2015 at 6:36 PM, Olga Kornievskaia wrote: > Client can receives stateid-type error (eg., BAD_STATEID) on SETATTR > when delegation stateid was used. When no open state exists, in case > of application calling truncate() on the file, client has no state to > recover and fails with EIO. > > Instead, upon such error, return the bad delegation and then resend the > SETATTR with a zero stateid. In general, when something calls > nfs4_handle_exception() with a null state, the operation should be > retried after bad delegation is removed. > > Signed-off: Olga Kornievskaia > --- > fs/nfs/nfs4proc.c | 5 ++++- > 1 file changed, 4 insertions(+), 1 deletion(-) > > diff --git a/fs/nfs/nfs4proc.c b/fs/nfs/nfs4proc.c > index ad7cf7e..fbde292 100644 > --- a/fs/nfs/nfs4proc.c > +++ b/fs/nfs/nfs4proc.c > @@ -360,8 +360,11 @@ static int nfs4_handle_exception(struct > nfs_server *server, int errorcode, struc > case -NFS4ERR_DELEG_REVOKED: > case -NFS4ERR_ADMIN_REVOKED: > case -NFS4ERR_BAD_STATEID: > - if (state == NULL) > + if (state == NULL) { > + nfs4_inode_return_delegation(inode); > + exception->retry = 1; > break; > + } > ret = nfs4_schedule_stateid_recovery(server, state); > if (ret < 0) > break; > --