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: check NULL return value in gfs2_ok_to_move
Date: Wed, 12 Mar 2014 10:03:20 +0000	[thread overview]
Message-ID: <1394618600.2729.37.camel@menhir> (raw)
In-Reply-To: <1394613704-30146-1-git-send-email-adas@redhat.com>

Hi,

On Wed, 2014-03-12 at 03:41 -0500, Abhi Das wrote:
> gfs2_lookupi() can return NULL if the path to the root is broken by
> another rename/rmdir. In this case gfs2_ok_to_move() must check for
> this NULL pointer and return error.
> 
> Resolves: rhbz#1060246
> Signed-off-by: Abhi Das <adas@redhat.com>

Thanks for the patch. I've added it to the -nmw tree,

Steve.

> ---
>  fs/gfs2/inode.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/fs/gfs2/inode.c b/fs/gfs2/inode.c
> index ec455b9..b52ebf8 100644
> --- a/fs/gfs2/inode.c
> +++ b/fs/gfs2/inode.c
> @@ -1299,6 +1299,10 @@ static int gfs2_ok_to_move(struct gfs2_inode *this, struct gfs2_inode *to)
>  		}
>  
>  		tmp = gfs2_lookupi(dir, &gfs2_qdotdot, 1);
> +		if (!tmp) {
> +			error = -ENOENT;
> +			break;
> +		}
>  		if (IS_ERR(tmp)) {
>  			error = PTR_ERR(tmp);
>  			break;




  reply	other threads:[~2014-03-12 10:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-12  8:41 [Cluster-devel] [GFS2 PATCH] GFS2: check NULL return value in gfs2_ok_to_move Abhi Das
2014-03-12 10:03 ` Steven Whitehouse [this message]
2014-03-12 10:59   ` Abhijith Das
2014-03-12 13:08     ` Steven Whitehouse

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=1394618600.2729.37.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).