linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brian Foster <bfoster@redhat.com>
To: Christoph Hellwig <hch@lst.de>
Cc: linux-xfs@vger.kernel.org, "Darrick J. Wong" <darrick.wong@oracle.com>
Subject: Re: [PATCH 1/6] xfs: clean up xchk_bmap_check_rmaps usage of XFS_IFORK_Q
Date: Mon, 18 May 2020 09:28:08 -0400	[thread overview]
Message-ID: <20200518132808.GD10938@bfoster> (raw)
In-Reply-To: <20200518073358.760214-2-hch@lst.de>

On Mon, May 18, 2020 at 09:33:53AM +0200, Christoph Hellwig wrote:
> From: "Darrick J. Wong" <darrick.wong@oracle.com>
> 
> XFS_IFORK_Q is supposed to be a predicate, not a function returning a
> value.  Its usage is in xchk_bmap_check_rmaps is incorrect, but that
> function only cares about whether or not the "size" of the data is zero
> or not.  Convert that logic to use a proper boolean, and teach the
> caller to skip the call entirely if the end result would be that we'd do
> nothing anyway.  This avoids a crash later in this series.
> 
> Signed-off-by: Darrick J. Wong <darrick.wong@oracle.com>
> [hch: generalized the NULL ifor check]
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---

I'm still rather confused about the i_size logic, but this seems like a
good cleanup regardless:

Reviewed-by: Brian Foster <bfoster@redhat.com>

>  fs/xfs/scrub/bmap.c | 35 +++++++++++++----------------------
>  1 file changed, 13 insertions(+), 22 deletions(-)
> 
> diff --git a/fs/xfs/scrub/bmap.c b/fs/xfs/scrub/bmap.c
> index add8598eacd5d..d0daf3de9fde5 100644
> --- a/fs/xfs/scrub/bmap.c
> +++ b/fs/xfs/scrub/bmap.c
> @@ -566,8 +566,8 @@ xchk_bmap_check_rmaps(
>  	struct xfs_scrub	*sc,
>  	int			whichfork)
>  {
> -	loff_t			size;
>  	xfs_agnumber_t		agno;
> +	bool			zero_size;
>  	int			error;
>  
>  	if (!xfs_sb_version_hasrmapbt(&sc->mp->m_sb) ||
> @@ -579,6 +579,8 @@ xchk_bmap_check_rmaps(
>  	if (XFS_IS_REALTIME_INODE(sc->ip) && whichfork == XFS_DATA_FORK)
>  		return 0;
>  
> +	ASSERT(XFS_IFORK_PTR(sc->ip, whichfork) != NULL);
> +
>  	/*
>  	 * Only do this for complex maps that are in btree format, or for
>  	 * situations where we would seem to have a size but zero extents.
> @@ -586,19 +588,13 @@ xchk_bmap_check_rmaps(
>  	 * to flag this bmap as corrupt if there are rmaps that need to be
>  	 * reattached.
>  	 */
> -	switch (whichfork) {
> -	case XFS_DATA_FORK:
> -		size = i_size_read(VFS_I(sc->ip));
> -		break;
> -	case XFS_ATTR_FORK:
> -		size = XFS_IFORK_Q(sc->ip);
> -		break;
> -	default:
> -		size = 0;
> -		break;
> -	}
> +	if (whichfork == XFS_DATA_FORK)
> +		zero_size = i_size_read(VFS_I(sc->ip)) == 0;
> +	else
> +		zero_size = false;
> +
>  	if (XFS_IFORK_FORMAT(sc->ip, whichfork) != XFS_DINODE_FMT_BTREE &&
> -	    (size == 0 || XFS_IFORK_NEXTENTS(sc->ip, whichfork) > 0))
> +	    (zero_size || XFS_IFORK_NEXTENTS(sc->ip, whichfork) > 0))
>  		return 0;
>  
>  	for (agno = 0; agno < sc->mp->m_sb.sb_agcount; agno++) {
> @@ -627,12 +623,14 @@ xchk_bmap(
>  	struct xchk_bmap_info	info = { NULL };
>  	struct xfs_mount	*mp = sc->mp;
>  	struct xfs_inode	*ip = sc->ip;
> -	struct xfs_ifork	*ifp;
> +	struct xfs_ifork	*ifp = XFS_IFORK_PTR(ip, whichfork);
>  	xfs_fileoff_t		endoff;
>  	struct xfs_iext_cursor	icur;
>  	int			error = 0;
>  
> -	ifp = XFS_IFORK_PTR(ip, whichfork);
> +	/* Non-existent forks can be ignored. */
> +	if (!ifp)
> +		goto out;
>  
>  	info.is_rt = whichfork == XFS_DATA_FORK && XFS_IS_REALTIME_INODE(ip);
>  	info.whichfork = whichfork;
> @@ -641,9 +639,6 @@ xchk_bmap(
>  
>  	switch (whichfork) {
>  	case XFS_COW_FORK:
> -		/* Non-existent CoW forks are ignorable. */
> -		if (!ifp)
> -			goto out;
>  		/* No CoW forks on non-reflink inodes/filesystems. */
>  		if (!xfs_is_reflink_inode(ip)) {
>  			xchk_ino_set_corrupt(sc, sc->ip->i_ino);
> @@ -651,8 +646,6 @@ xchk_bmap(
>  		}
>  		break;
>  	case XFS_ATTR_FORK:
> -		if (!ifp)
> -			goto out_check_rmap;
>  		if (!xfs_sb_version_hasattr(&mp->m_sb) &&
>  		    !xfs_sb_version_hasattr2(&mp->m_sb))
>  			xchk_ino_set_corrupt(sc, sc->ip->i_ino);
> @@ -700,7 +693,6 @@ xchk_bmap(
>  
>  	/* Scrub extent records. */
>  	info.lastoff = 0;
> -	ifp = XFS_IFORK_PTR(ip, whichfork);
>  	for_each_xfs_iext(ifp, &icur, &irec) {
>  		if (xchk_should_terminate(sc, &error) ||
>  		    (sc->sm->sm_flags & XFS_SCRUB_OFLAG_CORRUPT))
> @@ -717,7 +709,6 @@ xchk_bmap(
>  			goto out;
>  	}
>  
> -out_check_rmap:
>  	error = xchk_bmap_check_rmaps(sc, whichfork);
>  	if (!xchk_fblock_xref_process_error(sc, whichfork, 0, &error))
>  		goto out;
> -- 
> 2.26.2
> 


  reply	other threads:[~2020-05-18 13:28 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-18  7:33 move the extent count and format into struct xfs_ifork v2 Christoph Hellwig
2020-05-18  7:33 ` [PATCH 1/6] xfs: clean up xchk_bmap_check_rmaps usage of XFS_IFORK_Q Christoph Hellwig
2020-05-18 13:28   ` Brian Foster [this message]
2020-05-18  7:33 ` [PATCH 2/6] xfs: remove the XFS_DFORK_Q macro Christoph Hellwig
2020-05-18  7:33 ` [PATCH 3/6] xfs: remove xfs_ifree_local_data Christoph Hellwig
2020-05-18  7:33 ` [PATCH 4/6] xfs: move the per-fork nextents fields into struct xfs_ifork Christoph Hellwig
2020-05-18  7:33 ` [PATCH 5/6] xfs: move the fork format " Christoph Hellwig
2020-05-18  7:33 ` [PATCH 6/6] xfs: cleanup xfs_idestroy_fork Christoph Hellwig
2020-05-18 13:28   ` Brian Foster

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=20200518132808.GD10938@bfoster \
    --to=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=hch@lst.de \
    --cc=linux-xfs@vger.kernel.org \
    /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).