From: Steven Whitehouse <swhiteho@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [GFS2 PATCH] [bz878476] - Fix race in gfs2_rs_alloc
Date: Wed, 19 Dec 2012 16:23:10 +0000 [thread overview]
Message-ID: <1355934190.2740.33.camel@menhir> (raw)
In-Reply-To: <1725701894.66056191.1355932081651.JavaMail.root@redhat.com>
Hi,
I've added that to my tree of pending patches. That will be in the -nmw
tree just as soon as -rc1 is out. Thanks,
Steve.
On Wed, 2012-12-19 at 10:48 -0500, Abhijith Das wrote:
> QE aio tests uncovered a race condition in gfs2_rs_alloc where it's possible to come out of the function with a valid ip->i_res allocation but it gets freed before use resulting in a NULL ptr dereference.
>
> This patch envelopes the initial short-circuit check for non-NULL ip->i_res into the mutex lock. With this patch, I was able to successfully run the reproducer test multiple times.
>
> Resolves: rhbz#878476
> Signed-off-by: Abhi Das <adas@redhat.com>
>
> diff --git a/fs/gfs2/rgrp.c b/fs/gfs2/rgrp.c
> index 37ee061..738b388 100644
> --- a/fs/gfs2/rgrp.c
> +++ b/fs/gfs2/rgrp.c
> @@ -557,22 +557,20 @@ void gfs2_free_clones(struct gfs2_rgrpd *rgd)
> */
> int gfs2_rs_alloc(struct gfs2_inode *ip)
> {
> - struct gfs2_blkreserv *res;
> + int error = 0;
>
> + down_write(&ip->i_rw_mutex);
> if (ip->i_res)
> - return 0;
> -
> - res = kmem_cache_zalloc(gfs2_rsrv_cachep, GFP_NOFS);
> - if (!res)
> - return -ENOMEM;
> + goto out;
>
> - RB_CLEAR_NODE(&res->rs_node);
> + ip->i_res = kmem_cache_zalloc(gfs2_rsrv_cachep, GFP_NOFS);
> + if (!ip->i_res) {
> + error = -ENOMEM;
> + goto out;
> + }
>
> - down_write(&ip->i_rw_mutex);
> - if (ip->i_res)
> - kmem_cache_free(gfs2_rsrv_cachep, res);
> - else
> - ip->i_res = res;
> + RB_CLEAR_NODE(&ip->i_res->rs_node);
> +out:
> up_write(&ip->i_rw_mutex);
> return 0;
> }
>
prev parent reply other threads:[~2012-12-19 16:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-19 15:48 [Cluster-devel] [GFS2 PATCH] [bz878476] - Fix race in gfs2_rs_alloc Abhijith Das
2012-12-19 16:23 ` 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=1355934190.2740.33.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).