From: David Ahern <dsa@cumulusnetworks.com>
To: netdev@vger.kernel.org
Cc: David Ahern <dsa@cumulusnetworks.com>
Subject: [PATCH net-next] net: Add tos to validate source tracepoint
Date: Mon, 31 Aug 2015 09:57:12 -0600 [thread overview]
Message-ID: <1441036632-26203-1-git-send-email-dsa@cumulusnetworks.com> (raw)
TOS is another key aspect of the lookup passed to fib_validate_source.
Add it to the tracepoint.
Signed-off-by: David Ahern <dsa@cumulusnetworks.com>
---
include/trace/events/fib.h | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/include/trace/events/fib.h b/include/trace/events/fib.h
index 4030f75410d7..acd1d22571a2 100644
--- a/include/trace/events/fib.h
+++ b/include/trace/events/fib.h
@@ -83,6 +83,7 @@ TRACE_EVENT(fib_validate_source,
__string( name, dev->name )
__field( int, oif )
__field( int, iif )
+ __field( __u8, tos )
__array( __u8, src, 4 )
__array( __u8, dst, 4 )
),
@@ -93,6 +94,7 @@ TRACE_EVENT(fib_validate_source,
__assign_str(name, dev ? dev->name : "not set");
__entry->oif = flp->flowi4_oif;
__entry->iif = flp->flowi4_iif;
+ __entry->tos = flp->flowi4_tos;
p32 = (__be32 *) __entry->src;
*p32 = flp->saddr;
@@ -101,8 +103,8 @@ TRACE_EVENT(fib_validate_source,
*p32 = flp->daddr;
),
- TP_printk("dev %s oif %d iif %d src %pI4 dst %pI4",
- __get_str(name), __entry->oif, __entry->iif,
+ TP_printk("dev %s oif %d iif %d tos %d src %pI4 dst %pI4",
+ __get_str(name), __entry->oif, __entry->iif, __entry->tos,
__entry->src, __entry->dst)
);
#endif /* _TRACE_FIB_H */
--
2.3.2 (Apple Git-55)
next reply other threads:[~2015-08-31 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-31 15:57 David Ahern [this message]
2015-08-31 19:42 ` [PATCH net-next] net: Add tos to validate source tracepoint David Miller
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=1441036632-26203-1-git-send-email-dsa@cumulusnetworks.com \
--to=dsa@cumulusnetworks.com \
--cc=netdev@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).