linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Jeff Layton <jlayton@redhat.com>
Cc: linux-nfs@vger.kernel.org, steved@redhat.com
Subject: Re: [PATCH] nfs: handle lock context allocation failures in nfs_create_request
Date: Thu, 28 Oct 2010 14:17:39 -0400	[thread overview]
Message-ID: <1288289859.14221.13.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <1288275037-22816-1-git-send-email-jlayton@redhat.com>

On Thu, 2010-10-28 at 10:10 -0400, Jeff Layton wrote:
> nfs_get_lock_context can return NULL on an allocation failure.
> 
> Reported-by: Steve Dickson <steved@redhat.com>
> Signed-off-by: Jeff Layton <jlayton@redhat.com>
> ---
>  fs/nfs/pagelist.c |    8 +++++++-
>  1 files changed, 7 insertions(+), 1 deletions(-)
> 
> diff --git a/fs/nfs/pagelist.c b/fs/nfs/pagelist.c
> index 9194902..137b549 100644
> --- a/fs/nfs/pagelist.c
> +++ b/fs/nfs/pagelist.c
> @@ -65,6 +65,13 @@ nfs_create_request(struct nfs_open_context *ctx, struct inode *inode,
>  	if (req == NULL)
>  		return ERR_PTR(-ENOMEM);
>  
> +	/* get lock context early so we can deal with alloc failures */
> +	req->wb_lock_context = nfs_get_lock_context(ctx);
> +	if (req->wb_lock_context == NULL) {
> +		nfs_page_free(req);
> +		return ERR_PTR(-ENOMEM);
> +	}
> +
>  	/* Initialize the request struct. Initially, we assume a
>  	 * long write-back delay. This will be adjusted in
>  	 * update_nfs_request below if the region is not locked. */
> @@ -79,7 +86,6 @@ nfs_create_request(struct nfs_open_context *ctx, struct inode *inode,
>  	req->wb_pgbase	= offset;
>  	req->wb_bytes   = count;
>  	req->wb_context = get_nfs_open_context(ctx);
> -	req->wb_lock_context = nfs_get_lock_context(ctx);
>  	kref_init(&req->wb_kref);
>  	return req;
>  }

Thanks! Applied!

Trond

      reply	other threads:[~2010-10-28 18:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 14:10 [PATCH] nfs: handle lock context allocation failures in nfs_create_request Jeff Layton
2010-10-28 18:17 ` Trond Myklebust [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=1288289859.14221.13.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=jlayton@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=steved@redhat.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).