From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug tapsets/13793] New: IPv6 nfs_proc.stp tapset changes needed
Date: Thu, 01 Mar 2012 17:29:00 -0000 [thread overview]
Message-ID: <bug-13793-6586@http.sourceware.org/bugzilla/> (raw)
http://sourceware.org/bugzilla/show_bug.cgi?id=13793
Bug #: 13793
Summary: IPv6 nfs_proc.stp tapset changes needed
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
AssignedTo: systemtap@sourceware.org
ReportedBy: dsmith@redhat.com
Depends on: 13646
Classification: Unclassified
The nfs_proc.stp tapset is full of probes that return 'server_ip', a binary IP
address of the server. A typical line to generate that value looks like this:
server_ip = __i2n_ip_proto($dir,0)
That works fine for IPv4. That binary value can be used in comparisons, as an
array index, etc. However, the above doesn't work for IPv6. That function (if
it supported IPv6) would return the address of a structure that holds the IPv6
address.
Those probes should be changed to return a string representation of the IP
address, which can be compared properly for both IPv4 and IPv6.
(Bug #13646 provided the base tapset IPv6 support.)
--
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next reply other threads:[~2012-03-01 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 17:29 dsmith at redhat dot com [this message]
2012-03-01 17:32 ` [Bug tapsets/13793] " dsmith at redhat dot com
2020-05-26 18:41 ` sapatel at redhat dot com
2020-05-26 19:03 ` alizhang at redhat dot com
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-13793-6586@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).