Linux XFS filesystem development
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Guo Xuenan <guoxuenan@huawei.com>
Cc: dchinner@redhat.com, linux-xfs@vger.kernel.org,
	sandeen@redhat.com, guoxuenan@huaweicloud.com,
	houtao1@huawei.com, fangwei1@huawei.com, jack.qiu@huawei.com,
	yi.zhang@huawei.com
Subject: Re: [PATCH v2 2/2] xfs: clean up some unnecessary xfs_stack_trace
Date: Fri, 21 Apr 2023 20:57:20 -0700	[thread overview]
Message-ID: <20230422035720.GN360889@frogsfrogsfrogs> (raw)
In-Reply-To: <20230421113716.1890274-3-guoxuenan@huawei.com>

On Fri, Apr 21, 2023 at 07:37:16PM +0800, Guo Xuenan wrote:
> With xfs print level parsing correctly, these duplicate dump
> information can be removed.
> 
> Signed-off-by: Guo Xuenan <guoxuenan@huawei.com>
> ---
>  fs/xfs/libxfs/xfs_ialloc.c | 1 -
>  fs/xfs/xfs_error.c         | 9 ---------
>  fs/xfs/xfs_fsops.c         | 2 --
>  fs/xfs/xfs_log.c           | 2 --
>  4 files changed, 14 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_ialloc.c b/fs/xfs/libxfs/xfs_ialloc.c
> index a16d5de16933..df4e4eb19f14 100644
> --- a/fs/xfs/libxfs/xfs_ialloc.c
> +++ b/fs/xfs/libxfs/xfs_ialloc.c
> @@ -2329,7 +2329,6 @@ xfs_imap(
>  				__func__, ino,
>  				XFS_AGINO_TO_INO(mp, pag->pag_agno, agino));
>  		}
> -		xfs_stack_trace();

Hmm, this one was unconditional, wasn't it?  That looks like an omission
to me, so I'm calling it out in case anyone had hard opinions about it.
Otherwise,

Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

>  #endif /* DEBUG */
>  		return error;
>  	}
> diff --git a/fs/xfs/xfs_error.c b/fs/xfs/xfs_error.c
> index b2cbbba3e15a..7c8e1f3b69a6 100644
> --- a/fs/xfs/xfs_error.c
> +++ b/fs/xfs/xfs_error.c
> @@ -421,9 +421,6 @@ xfs_buf_corruption_error(
>  		  fa, bp->b_ops->name, xfs_buf_daddr(bp));
>  
>  	xfs_alert(mp, "Unmount and run xfs_repair");
> -
> -	if (xfs_error_level >= XFS_ERRLEVEL_HIGH)
> -		xfs_stack_trace();
>  }
>  
>  /*
> @@ -459,9 +456,6 @@ xfs_buf_verifier_error(
>  				sz);
>  		xfs_hex_dump(buf, sz);
>  	}
> -
> -	if (xfs_error_level >= XFS_ERRLEVEL_HIGH)
> -		xfs_stack_trace();
>  }
>  
>  /*
> @@ -509,7 +503,4 @@ xfs_inode_verifier_error(
>  				sz);
>  		xfs_hex_dump(buf, sz);
>  	}
> -
> -	if (xfs_error_level >= XFS_ERRLEVEL_HIGH)
> -		xfs_stack_trace();
>  }
> diff --git a/fs/xfs/xfs_fsops.c b/fs/xfs/xfs_fsops.c
> index 13851c0d640b..e08b1ce109d9 100644
> --- a/fs/xfs/xfs_fsops.c
> +++ b/fs/xfs/xfs_fsops.c
> @@ -546,8 +546,6 @@ xfs_do_force_shutdown(
>  			why, flags, __return_address, fname, lnnum);
>  	xfs_alert(mp,
>  		"Please unmount the filesystem and rectify the problem(s)");
> -	if (xfs_error_level >= XFS_ERRLEVEL_HIGH)
> -		xfs_stack_trace();
>  }
>  
>  /*
> diff --git a/fs/xfs/xfs_log.c b/fs/xfs/xfs_log.c
> index fc61cc024023..e4e4da33281d 100644
> --- a/fs/xfs/xfs_log.c
> +++ b/fs/xfs/xfs_log.c
> @@ -3808,8 +3808,6 @@ xlog_force_shutdown(
>  				shutdown_flags);
>  		xfs_alert(log->l_mp,
>  "Please unmount the filesystem and rectify the problem(s).");
> -		if (xfs_error_level >= XFS_ERRLEVEL_HIGH)
> -			xfs_stack_trace();
>  	}
>  
>  	/*
> -- 
> 2.31.1
> 

  reply	other threads:[~2023-04-22  3:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21 11:37 [PATCH v2 0/2] xfs fix and clean up Guo Xuenan
2023-04-21 11:37 ` [PATCH v2 1/2] xfs: fix xfs print level wrong parsing Guo Xuenan
2023-04-22  3:55   ` Darrick J. Wong
2023-04-21 11:37 ` [PATCH v2 2/2] xfs: clean up some unnecessary xfs_stack_trace Guo Xuenan
2023-04-22  3:57   ` Darrick J. Wong [this message]
2023-04-23  1:44     ` Guo Xuenan

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=20230422035720.GN360889@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=dchinner@redhat.com \
    --cc=fangwei1@huawei.com \
    --cc=guoxuenan@huawei.com \
    --cc=guoxuenan@huaweicloud.com \
    --cc=houtao1@huawei.com \
    --cc=jack.qiu@huawei.com \
    --cc=linux-xfs@vger.kernel.org \
    --cc=sandeen@redhat.com \
    --cc=yi.zhang@huawei.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