public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Ben Myers <bpm@sgi.com>
To: Jeff Liu <jeff.liu@oracle.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: Remove redundant return error from xfs_difree()
Date: Fri, 2 Nov 2012 16:05:18 -0500	[thread overview]
Message-ID: <20121102210518.GH9783@sgi.com> (raw)
In-Reply-To: <5088BFD5.8060906@oracle.com>

Hey Jeff,

On Thu, Oct 25, 2012 at 12:28:05PM +0800, Jeff Liu wrote:
> If we can not fetch the related a.g. info when freeing a disk inode, it mostly like a
> fatal issue was occurred and with ASSERT(0) is fine, however, return XFS_ERROR(EINVAL)
> does not make sense here.
> 
> Signed-off-by: Jie Liu <jeff.liu@oracle.com>
> 
> ---
>  fs/xfs/xfs_ialloc.c |    3 ---
>  1 files changed, 0 insertions(+), 3 deletions(-)
> 
> diff --git a/fs/xfs/xfs_ialloc.c b/fs/xfs/xfs_ialloc.c
> index 445bf1a..b7ea965 100644
> --- a/fs/xfs/xfs_ialloc.c
> +++ b/fs/xfs/xfs_ialloc.c
> @@ -1065,7 +1065,6 @@ xfs_difree(
>  		xfs_warn(mp, "%s: agno >= mp->m_sb.sb_agcount (%d >= %d).",
>  			__func__, agno, mp->m_sb.sb_agcount);
>  		ASSERT(0);
> -		return XFS_ERROR(EINVAL);
>  	}
>  	agino = XFS_INO_TO_AGINO(mp, inode);
>  	if (inode != XFS_AGINO_TO_INO(mp, agno, agino))  {
> @@ -1073,14 +1072,12 @@ xfs_difree(
>  			__func__, (unsigned long long)inode,
>  			(unsigned long long)XFS_AGINO_TO_INO(mp, agno, agino));
>  		ASSERT(0);
> -		return XFS_ERROR(EINVAL);
>  	}
>  	agbno = XFS_AGINO_TO_AGBNO(mp, agino);
>  	if (agbno >= mp->m_sb.sb_agblocks)  {
>  		xfs_warn(mp, "%s: agbno >= mp->m_sb.sb_agblocks (%d >= %d).",
>  			__func__, agbno, mp->m_sb.sb_agblocks);
>  		ASSERT(0);
> -		return XFS_ERROR(EINVAL);
>  	}
>  	/*
>  	 * Get the allocation group header.

Here the return of EINVAL is serving a useful purpose.  The ASSERT is only
activated when xfs debug is configured on, so there is a very real chance that
you might exercise this code.

My read on this is if you pass bad args to xfs_difree it will return EINVAL.
It's just a little defensive coding but it's worth keeping.  In this case it
will result in forced shutdown of the filesystem, which is much better than the
[unspecified] baddness that could happen later in xfs_difree if you have passed
in garbage args.

There... I got my FUD in for the day.  ;)

Thanks for the patch, but I think we need to pass on this one.

Regards,
Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2012-11-02 21:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-25  4:28 [PATCH] xfs: Remove redundant return error from xfs_difree() Jeff Liu
2012-11-02 21:05 ` Ben Myers [this message]
2012-11-03  4:28   ` Jeff Liu

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=20121102210518.GH9783@sgi.com \
    --to=bpm@sgi.com \
    --cc=jeff.liu@oracle.com \
    --cc=xfs@oss.sgi.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