From: Chuck Lever III <chuck.lever@oracle.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Linux NFS Mailing List <linux-nfs@vger.kernel.org>,
"linux-trace-devel@vger.kernel.org"
<linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH v2 0/2] Fix sockaddr handling in NFSD trace points
Date: Tue, 11 Jan 2022 15:40:42 +0000 [thread overview]
Message-ID: <024057EF-19AC-4AAA-8C1C-EADD6087DF32@oracle.com> (raw)
In-Reply-To: <20220110183133.78098878@gandalf.local.home>
> On Jan 10, 2022, at 6:31 PM, Steven Rostedt <rostedt@goodmis.org> wrote:
>
> On Mon, 10 Jan 2022 11:05:35 -0500
> Steven Rostedt <rostedt@goodmis.org> wrote:
>
>>> I haven't quite been able to figure out how to handle the
>>> TP_printk() part of this equation. `trace-cmd report` displays
>>> something like "addr=ARG TYPE NOT FIELD BUT 7".
>>>
>>> Thoughts or advice appreciated.
>>
>> I'll take a look into it.
>
> If you add this to libtraceevent, it will work:
Thank you Steven! I will set up my current test system with
a locally-built trace-cmd and try this out. I can send a
proper patch that introduces the helper macros in my cover
letter's pseudo-code example today or tomorrow.
> diff --git a/src/event-parse.c b/src/event-parse.c
> index 9bd605d..033529c 100644
> --- a/src/event-parse.c
> +++ b/src/event-parse.c
> @@ -5127,6 +5127,8 @@ static int print_ipsa_arg(struct trace_seq *s, const char *ptr, char i,
> unsigned char *buf;
> struct sockaddr_storage *sa;
> bool reverse = false;
> + unsigned int offset;
> + unsigned int len;
> int rc = 0;
> int ret;
>
> @@ -5152,27 +5154,42 @@ static int print_ipsa_arg(struct trace_seq *s, const char *ptr, char i,
> return rc;
> }
>
> - if (arg->type != TEP_PRINT_FIELD) {
> - trace_seq_printf(s, "ARG TYPE NOT FIELD BUT %d", arg->type);
> - return rc;
> - }
> + /* evaluate if the arg has a typecast */
> + while (arg->type == TEP_PRINT_TYPE)
> + arg = arg->typecast.item;
> +
> + if (arg->type == TEP_PRINT_FIELD) {
>
> - if (!arg->field.field) {
> - arg->field.field =
> - tep_find_any_field(event, arg->field.name);
> if (!arg->field.field) {
> - do_warning("%s: field %s not found",
> - __func__, arg->field.name);
> - return rc;
> + arg->field.field =
> + tep_find_any_field(event, arg->field.name);
> + if (!arg->field.field) {
> + do_warning("%s: field %s not found",
> + __func__, arg->field.name);
> + return rc;
> + }
> }
> +
> + offset = arg->field.field->offset;
> + len = arg->field.field->size;
> +
> + } else if (arg->type == TEP_PRINT_DYNAMIC_ARRAY) {
> +
> + dynamic_offset_field(event->tep, arg->dynarray.field, data,
> + size, &offset, &len);
> +
> + } else {
> + trace_seq_printf(s, "ARG NOT FIELD NOR DYNAMIC ARRAY BUT TYPE %d",
> + arg->type);
> + return rc;
> }
>
> - sa = (struct sockaddr_storage *) (data + arg->field.field->offset);
> + sa = (struct sockaddr_storage *)(data + offset);
>
> if (sa->ss_family == AF_INET) {
> struct sockaddr_in *sa4 = (struct sockaddr_in *) sa;
>
> - if (arg->field.field->size < sizeof(struct sockaddr_in)) {
> + if (len < sizeof(struct sockaddr_in)) {
> trace_seq_printf(s, "INVALIDIPv4");
> return rc;
> }
> @@ -5185,7 +5202,7 @@ static int print_ipsa_arg(struct trace_seq *s, const char *ptr, char i,
> } else if (sa->ss_family == AF_INET6) {
> struct sockaddr_in6 *sa6 = (struct sockaddr_in6 *) sa;
>
> - if (arg->field.field->size < sizeof(struct sockaddr_in6)) {
> + if (len < sizeof(struct sockaddr_in6)) {
> trace_seq_printf(s, "INVALIDIPv6");
> return rc;
> }
--
Chuck Lever
prev parent reply other threads:[~2022-01-11 15:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 15:56 [PATCH v2 0/2] Fix sockaddr handling in NFSD trace points Chuck Lever
2022-01-10 15:56 ` [PATCH v2 1/2] SUNRPC: Fix sockaddr handling in the svc_xprt_create_error trace point Chuck Lever
2022-01-10 15:57 ` [PATCH v2 2/2] SUNRPC: Fix sockaddr handling in svcsock_accept_class trace points Chuck Lever
2022-01-10 16:05 ` [PATCH v2 0/2] Fix sockaddr handling in NFSD " Steven Rostedt
2022-01-10 23:31 ` Steven Rostedt
2022-01-11 15:40 ` Chuck Lever III [this message]
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=024057EF-19AC-4AAA-8C1C-EADD6087DF32@oracle.com \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.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