From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@redhat.com>
Cc: linux-xfs <linux-xfs@vger.kernel.org>
Subject: Re: [PATCH] xfs: trace ATTR flags in xattr tracepoints
Date: Tue, 17 Apr 2018 17:37:12 -0700 [thread overview]
Message-ID: <20180418003712.GJ24738@magnolia> (raw)
In-Reply-To: <67a92fac-3e86-03c1-759e-af192d35e06b@redhat.com>
On Tue, Apr 17, 2018 at 03:03:32PM -0500, Eric Sandeen wrote:
> This will trace i.e. the ATTR_SECURE/ATTR_CREATE/ATTR_REPLACE
> flags as well as the OP_FLAGS.
>
> Signed-off-by: Eric Sandeen <sandeen@redhat.com>
Looks ok, will pick up for 4.18.
Reviewed-by: Darrick J. Wong <darrick.wong@oracle.com>
--D
> ---
>
> diff --git a/fs/xfs/xfs_trace.h b/fs/xfs/xfs_trace.h
> index 8955254..b03a0f4 100644
> --- a/fs/xfs/xfs_trace.h
> +++ b/fs/xfs/xfs_trace.h
> @@ -1750,6 +1750,7 @@
> __field(int, namelen)
> __field(int, valuelen)
> __field(xfs_dahash_t, hashval)
> + __field(int, flags)
> __field(int, op_flags)
> ),
> TP_fast_assign(
> @@ -1760,10 +1761,11 @@
> __entry->namelen = args->namelen;
> __entry->valuelen = args->valuelen;
> __entry->hashval = args->hashval;
> + __entry->flags = args->flags;
> __entry->op_flags = args->op_flags;
> ),
> TP_printk("dev %d:%d ino 0x%llx name %.*s namelen %d valuelen %d "
> - "hashval 0x%x op_flags %s",
> + "hashval 0x%x flags %s op_flags %s",
> MAJOR(__entry->dev), MINOR(__entry->dev),
> __entry->ino,
> __entry->namelen,
> @@ -1771,6 +1773,7 @@
> __entry->namelen,
> __entry->valuelen,
> __entry->hashval,
> + __print_flags(__entry->flags, "|", XFS_ATTR_FLAGS),
> __print_flags(__entry->op_flags, "|", XFS_DA_OP_FLAGS))
> )
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-04-18 0:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-17 20:03 [PATCH] xfs: trace ATTR flags in xattr tracepoints Eric Sandeen
2018-04-18 0:37 ` Darrick J. Wong [this message]
2018-04-18 10:28 ` 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=20180418003712.GJ24738@magnolia \
--to=darrick.wong@oracle.com \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@redhat.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;
as well as URLs for NNTP newsgroup(s).