All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfsd41: Create the recovery entry for the NFSv4.1 client
Date: Thu, 14 Jan 2010 12:26:13 -0500	[thread overview]
Message-ID: <20100114172613.GD27670@fieldses.org> (raw)
In-Reply-To: <1260587449-29538-1-git-send-email-Ricardo.Labiaga@netapp.com>

On Fri, Dec 11, 2009 at 07:10:48PM -0800, Ricardo Labiaga wrote:
> Signed-off-by: Ricardo Labiaga <Ricardo.Labiaga@netapp.com>

Thanks, looks right--applied.

--b.

> ---
>  fs/nfsd/nfs4state.c |    4 +++-
>  1 files changed, 3 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/nfsd/nfs4state.c b/fs/nfsd/nfs4state.c
> index 2153f9b..32aa837 100644
> --- a/fs/nfsd/nfs4state.c
> +++ b/fs/nfsd/nfs4state.c
> @@ -2487,8 +2487,10 @@ nfsd4_process_open2(struct svc_rqst *rqstp, struct svc_fh *current_fh, struct nf
>  	}
>  	memcpy(&open->op_stateid, &stp->st_stateid, sizeof(stateid_t));
>  
> -	if (nfsd4_has_session(&resp->cstate))
> +	if (nfsd4_has_session(&resp->cstate)) {
>  		open->op_stateowner->so_confirmed = 1;
> +		nfsd4_create_clid_dir(open->op_stateowner->so_client);
> +	}
>  
>  	/*
>  	* Attempt to hand out a delegation. No error return, because the
> -- 
> 1.5.4.3
> 

      parent reply	other threads:[~2010-01-14 17:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-12  3:10 [PATCH] nfsd41: Create the recovery entry for the NFSv4.1 client Ricardo Labiaga
2009-12-12  3:10 ` [PATCH] nfsd41: nfsd4_decode_compound() does not recognize all ops Ricardo Labiaga
2009-12-17 15:54   ` J. Bruce Fields
2009-12-17 16:39     ` [PATCH] nfsd41: nfsd4_decode_compound() does not recognize allops Labiaga, Ricardo
2010-01-14 17:26 ` J. Bruce Fields [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100114172613.GD27670@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Ricardo.Labiaga@netapp.com \
    --cc=linux-nfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.