All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Kinglong Mee <kinglongmee@gmail.com>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 1/4] NFS4: Avoid NULL reference or double free in nfsd4_fslocs_free()
Date: Fri, 23 May 2014 09:58:09 -0400	[thread overview]
Message-ID: <20140523135809.GL25423@fieldses.org> (raw)
In-Reply-To: <537F37BD.9070005@gmail.com>

On Fri, May 23, 2014 at 07:57:49PM +0800, Kinglong Mee wrote:
> If fsloc_parse() failed at kzalloc(), fs/nfsd/export.c
>  411
>  412         fsloc->locations = kzalloc(fsloc->locations_count
>  413                         * sizeof(struct nfsd4_fs_location), GFP_KERNEL);
>  414         if (!fsloc->locations)
>  415                 return -ENOMEM;
> 
> svc_export_parse() will call nfsd4_fslocs_free() with fsloc->locations = NULL,
> so that, "kfree(fsloc->locations[i].path);" will cause a crash.
> 
> If fsloc_parse() failed after that, fsloc_parse() will call nfsd4_fslocs_free(),
> and svc_export_parse() will call it again, so that, a double free is caused.
> 
> This patch checks the fsloc->locations, and set to NULL after it be freed.

Applying this and 2/4.

--b.

> 
> Signed-off-by: Kinglong Mee <kinglongmee@gmail.com>
> ---
>  fs/nfsd/export.c | 12 +++++++++---
>  1 file changed, 9 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/nfsd/export.c b/fs/nfsd/export.c
> index 8513c59..9a41d3d 100644
> --- a/fs/nfsd/export.c
> +++ b/fs/nfsd/export.c
> @@ -295,13 +295,19 @@ svc_expkey_update(struct cache_detail *cd, struct svc_expkey *new,
>  
>  static void nfsd4_fslocs_free(struct nfsd4_fs_locations *fsloc)
>  {
> +	struct nfsd4_fs_location *locations = fsloc->locations;
>  	int i;
>  
> +	if (!locations)
> +		return;
> +
>  	for (i = 0; i < fsloc->locations_count; i++) {
> -		kfree(fsloc->locations[i].path);
> -		kfree(fsloc->locations[i].hosts);
> +		kfree(locations[i].path);
> +		kfree(locations[i].hosts);
>  	}
> -	kfree(fsloc->locations);
> +
> +	kfree(locations);
> +	fsloc->locations = NULL;
>  }
>  
>  static void svc_export_put(struct kref *ref)
> -- 
> 1.9.0
> 

      reply	other threads:[~2014-05-23 13:58 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-23 11:57 [PATCH 1/4] NFS4: Avoid NULL reference or double free in nfsd4_fslocs_free() Kinglong Mee
2014-05-23 13:58 ` 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=20140523135809.GL25423@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=kinglongmee@gmail.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.