linux-trace-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Cc: Chuck Lever III <chuck.lever@oracle.com>
Subject: [PATCH] libtraceevent: Add processing of __get_sockaddr() and __get_sockaddr_rel()
Date: Tue, 28 Jun 2022 12:23:50 -0400	[thread overview]
Message-ID: <20220628122350.434ec8df@gandalf.local.home> (raw)

From: "Steven Rostedt (Google)" <rostedt@goodmis.org>

The macros __get_sockaddr() and __get_sockaddr_rel() are now added in the
TRACE_EVENT() helper functions and can be used to retrieve dynamically
saved sockaddr structures that hold IP addresses. Update libtraceevent to
handle them.

Link: https://lore.kernel.org/all/25C37F40-7D8E-41C6-961F-0774C8138CCB@oracle.com/

Reported-by: Chuck Lever III <chuck.lever@oracle.com>
Signed-off-by: Steven Rostedt (Google) <rostedt@goodmis.org>
---
 src/event-parse.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/src/event-parse.c b/src/event-parse.c
index 823333a3bde4..b252c4d890a0 100644
--- a/src/event-parse.c
+++ b/src/event-parse.c
@@ -3485,7 +3485,9 @@ process_function(struct tep_event *event, struct tep_print_arg *arg,
 		return process_bitmask(event, arg, tok);
 	}
 	if (strcmp(token, "__get_dynamic_array") == 0 ||
-	    strcmp(token, "__get_rel_dynamic_array") == 0) {
+	    strcmp(token, "__get_rel_dynamic_array") == 0 ||
+	    strcmp(token, "__get_sockaddr") == 0 ||
+	    strcmp(token, "__get_sockaddr_rel") == 0) {
 		free_token(token);
 		return process_dynamic_array(event, arg, tok);
 	}
-- 
2.35.1


             reply	other threads:[~2022-06-28 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 16:23 Steven Rostedt [this message]
2022-09-09 18:00 ` [PATCH] libtraceevent: Add processing of __get_sockaddr() and __get_sockaddr_rel() Chuck Lever III
2022-09-09 18:31   ` Steven Rostedt

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=20220628122350.434ec8df@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=chuck.lever@oracle.com \
    --cc=linux-trace-devel@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).