public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug kprobes/23186] struct flowi4 not found in kernel<net/flow.h> on kernel 3.10.0-862.2.3.el7.x86_64
Date: Mon, 21 May 2018 17:26:00 -0000	[thread overview]
Message-ID: <bug-23186-6586-1TbCvZ6R8w@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-23186-6586@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=23186

David Smith <dsmith at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |dsmith at redhat dot com
         Resolution|---                         |WORKSFORME

--- Comment #1 from David Smith <dsmith at redhat dot com> ---
This is really a problem with net/flow.h. It doesn't include <linux/kernel.h>
and <linux/bug.h>, even though it uses items from those headers. So, to fix
this, you need to change your script from:

====
probe kprobe.function("udp_send_skb") {
    fl4 = pointer_arg(2)
    saddr = ip_ntop(@cast(fl4,"struct flowi4","kernel<net/flow.h>")->saddr)
        printf("%s\n",saddr)
}
====

to:

====
probe kprobe.function("udp_send_skb") {
    fl4 = pointer_arg(2)
    saddr =
ip_ntop(@cast(fl4,"flowi4","kernel<linux/kernel.h><linux/bug.h><net/flow.h>")->saddr)
        printf("%s\n",saddr)
}
====

-- 
You are receiving this mail because:
You are the assignee for the bug.

      reply	other threads:[~2018-05-21 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15 19:27 [Bug kprobes/23186] New: " cmedved at cloudamize dot com
2018-05-21 17:26 ` dsmith at redhat dot com [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=bug-23186-6586-1TbCvZ6R8w@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=systemtap@sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).