All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joseph Qi <joseph.qi@huawei.com>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] ocfs2: fix improper handling of return errno
Date: Mon, 23 May 2016 11:21:49 +0800	[thread overview]
Message-ID: <5742774D.9010007@huawei.com> (raw)
In-Reply-To: <1463970656-18413-1-git-send-email-zren@suse.com>

On 2016/5/23 10:30, Eric Ren wrote:
> Previously, if bad inode was found in ocfs2_iget(), -ESTALE was
> returned back to the caller anyway. Since commit d2b9d71a2da7
> ("ocfs2: check/fix inode block for online file check") can handle
> with return value from ocfs2_read_locked_inode() now, we know the
> exact errno returned for us.
> 
> Signed-off-by: Eric Ren <zren@suse.com>
Looks good to me, thanks.
Reviewed-by: Joseph Qi <joseph.qi@huawei.com>

> ---
>  fs/ocfs2/inode.c | 7 +------
>  1 file changed, 1 insertion(+), 6 deletions(-)
> 
> diff --git a/fs/ocfs2/inode.c b/fs/ocfs2/inode.c
> index ba495be..fee5ec6 100644
> --- a/fs/ocfs2/inode.c
> +++ b/fs/ocfs2/inode.c
> @@ -176,12 +176,7 @@ struct inode *ocfs2_iget(struct ocfs2_super *osb, u64 blkno, unsigned flags,
>  	}
>  	if (is_bad_inode(inode)) {
>  		iput(inode);
> -		if ((flags & OCFS2_FI_FLAG_FILECHECK_CHK) ||
> -		    (flags & OCFS2_FI_FLAG_FILECHECK_FIX))
> -			/* Return OCFS2_FILECHECK_ERR_XXX related errno */
> -			inode = ERR_PTR(rc);
> -		else
> -			inode = ERR_PTR(-ESTALE);
> +		inode = ERR_PTR(rc);
>  		goto bail;
>  	}
>  
> 

  reply	other threads:[~2016-05-23  3:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-23  2:30 [Ocfs2-devel] [PATCH] ocfs2: fix improper handling of return errno Eric Ren
2016-05-23  3:21 ` Joseph Qi [this message]
2016-05-23  5:34   ` Gang He

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=5742774D.9010007@huawei.com \
    --to=joseph.qi@huawei.com \
    --cc=ocfs2-devel@oss.oracle.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 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.