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] [PATCH] gfs2: fix potential NULL pointer dereference
Date: Tue, 12 Nov 2013 12:35:12 +0000	[thread overview]
Message-ID: <1384259712.2697.9.camel@menhir> (raw)
In-Reply-To: <1384259405-7913-1-git-send-email-mpn@google.com>

Hi,

Yes, good catch. Thanks, I'll add it to the tree,

Steve.

On Tue, 2013-11-12 at 13:30 +0100, Michal Nazarewicz wrote:
> From: Michal Nazarewicz <mina86@mina86.com>
> 
> Commit [e66cf1610: GFS2: Use lockref for glocks] replaced call:
>     atomic_read(&gi->gl->gl_ref) == 0
> with:
>     __lockref_is_dead(&gl->gl_lockref)
> therefore changing how gl is accessed, from gi->gl to plan gl.
> However, gl can be a NULL pointer, and so gi->gl needs to be
> used instead (which is guaranteed not to be NULL because fo
> the while loop checking that condition).
> 
> Signed-off-by: Michal Nazarewicz <mina86@mina86.com>
> ---
>  fs/gfs2/glock.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/fs/gfs2/glock.c b/fs/gfs2/glock.c
> index e66a800..c8420f7 100644
> --- a/fs/gfs2/glock.c
> +++ b/fs/gfs2/glock.c
> @@ -1899,7 +1899,8 @@ static int gfs2_glock_iter_next(struct gfs2_glock_iter *gi)
>  			gi->nhash = 0;
>  		}
>  	/* Skip entries for other sb and dead entries */
> -	} while (gi->sdp != gi->gl->gl_sbd || __lockref_is_dead(&gl->gl_lockref));
> +	} while (gi->sdp != gi->gl->gl_sbd ||
> +		 __lockref_is_dead(&gi->gl->gl_lockref));
>  
>  	return 0;
>  }




      reply	other threads:[~2013-11-12 12:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12 12:30 [Cluster-devel] [PATCH] gfs2: fix potential NULL pointer dereference Michal Nazarewicz
2013-11-12 12:35 ` 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=1384259712.2697.9.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).