linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <djwong@kernel.org>
To: Christoph Hellwig <hch@lst.de>
Cc: chandan.babu@oracle.com, linux-xfs@vger.kernel.org
Subject: Re: [PATCH 2/2] xfs: use the op name in trace_xlog_intent_recovery_failed
Date: Wed, 27 Dec 2023 22:27:10 -0800	[thread overview]
Message-ID: <20231228062710.GS361584@frogsfrogsfrogs> (raw)
In-Reply-To: <20231228061830.337279-2-hch@lst.de>

On Thu, Dec 28, 2023 at 06:18:30AM +0000, Christoph Hellwig wrote:
> Instead of tracing the address of the recovery handler, use the name
> in the defer op, similar to other defer ops related tracepoints.
> 
> Signed-off-by: Christoph Hellwig <hch@lst.de>

Yay fewer pointer shenanigans,
Reviewed-by: Darrick J. Wong <djwong@kernel.org>

--D

> ---
>  fs/xfs/libxfs/xfs_defer.c |  3 +--
>  fs/xfs/xfs_trace.h        | 14 ++++++++------
>  2 files changed, 9 insertions(+), 8 deletions(-)
> 
> diff --git a/fs/xfs/libxfs/xfs_defer.c b/fs/xfs/libxfs/xfs_defer.c
> index 785c92d2acaa73..e99d7890e614e1 100644
> --- a/fs/xfs/libxfs/xfs_defer.c
> +++ b/fs/xfs/libxfs/xfs_defer.c
> @@ -920,8 +920,7 @@ xfs_defer_finish_recovery(
>  
>  	error = ops->recover_work(dfp, capture_list);
>  	if (error)
> -		trace_xlog_intent_recovery_failed(mp, error,
> -				ops->recover_work);
> +		trace_xlog_intent_recovery_failed(mp, ops, error);
>  	return error;
>  }
>  
> diff --git a/fs/xfs/xfs_trace.h b/fs/xfs/xfs_trace.h
> index 0efcdb79d10e51..a986c52ff466bc 100644
> --- a/fs/xfs/xfs_trace.h
> +++ b/fs/xfs/xfs_trace.h
> @@ -145,21 +145,23 @@ DEFINE_ATTR_LIST_EVENT(xfs_attr_leaf_list);
>  DEFINE_ATTR_LIST_EVENT(xfs_attr_node_list);
>  
>  TRACE_EVENT(xlog_intent_recovery_failed,
> -	TP_PROTO(struct xfs_mount *mp, int error, void *function),
> -	TP_ARGS(mp, error, function),
> +	TP_PROTO(struct xfs_mount *mp, const struct xfs_defer_op_type *ops,
> +		 int error),
> +	TP_ARGS(mp, ops, error),
>  	TP_STRUCT__entry(
>  		__field(dev_t, dev)
> +		__string(name, ops->name)
>  		__field(int, error)
> -		__field(void *, function)
>  	),
>  	TP_fast_assign(
>  		__entry->dev = mp->m_super->s_dev;
> +		__assign_str(name, ops->name);
>  		__entry->error = error;
> -		__entry->function = function;
>  	),
> -	TP_printk("dev %d:%d error %d function %pS",
> +	TP_printk("dev %d:%d optype %s error %d",
>  		  MAJOR(__entry->dev), MINOR(__entry->dev),
> -		  __entry->error, __entry->function)
> +		  __get_str(name),
> +		  __entry->error)
>  );
>  
>  DECLARE_EVENT_CLASS(xfs_perag_class,
> -- 
> 2.39.2
> 
> 

  reply	other threads:[~2023-12-28  6:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-28  6:18 [PATCH 1/2] xfs: fix a use after free in xfs_defer_finish_recovery Christoph Hellwig
2023-12-28  6:18 ` [PATCH 2/2] xfs: use the op name in trace_xlog_intent_recovery_failed Christoph Hellwig
2023-12-28  6:27   ` Darrick J. Wong [this message]
2023-12-28  6:26 ` [PATCH 1/2] xfs: fix a use after free in xfs_defer_finish_recovery Darrick J. Wong
2023-12-28  6:47   ` Christoph Hellwig

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=20231228062710.GS361584@frogsfrogsfrogs \
    --to=djwong@kernel.org \
    --cc=chandan.babu@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).