cluster-devel.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] GFS2: fix regression in dir_double_exhash
Date: Fri, 14 Jun 2013 13:55:48 +0100	[thread overview]
Message-ID: <1371214548.2741.1.camel@menhir> (raw)
In-Reply-To: <712035815.65889203.1371213558262.JavaMail.root@redhat.com>

Hi,

Looks good. I'll push this to the -nmw tree shortly,

Steve.

On Fri, 2013-06-14 at 08:39 -0400, Bob Peterson wrote:
> Hi,
> 
> Recent commit e8830d8 introduced a bug in function dir_double_exhash;
> it was failing to set h in the fall-back case. This patch corrects it.
> 
> Regards,
> 
> Bob Peterson
> Red Hat File Systems
> 
> Signed-off-by: Bob Peterson <rpeterso@redhat.com> 
> ---
>  fs/gfs2/dir.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/dir.c b/fs/gfs2/dir.c
> index f0c7052..147fcc5 100644
> --- a/fs/gfs2/dir.c
> +++ b/fs/gfs2/dir.c
> @@ -1125,13 +1125,14 @@ static int dir_double_exhash(struct gfs2_inode *dip)
>  	if (IS_ERR(hc))
>  		return PTR_ERR(hc);
>  
> -	h = hc2 = kmalloc(hsize_bytes * 2, GFP_NOFS | __GFP_NOWARN);
> +	hc2 = kmalloc(hsize_bytes * 2, GFP_NOFS | __GFP_NOWARN);
>  	if (hc2 == NULL)
>  		hc2 = __vmalloc(hsize_bytes * 2, GFP_NOFS, PAGE_KERNEL);
>  
>  	if (!hc2)
>  		return -ENOMEM;
>  
> +	h = hc2;
>  	error = gfs2_meta_inode_buffer(dip, &dibh);
>  	if (error)
>  		goto out_kfree;
> 




      reply	other threads:[~2013-06-14 12:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1178155712.65865136.1371213053825.JavaMail.root@redhat.com>
2013-06-14 12:39 ` [Cluster-devel] [GFS2 PATCH] GFS2: fix regression in dir_double_exhash Bob Peterson
2013-06-14 12:55   ` Steven Whitehouse [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=1371214548.2741.1.camel@menhir \
    --to=swhiteho@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).