This is the mail archive of the
systemtap@sourceware.org
mailing list for the systemtap project.
[Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order
- From: "jistone at redhat dot com" <sourceware-bugzilla at sourceware dot org>
- To: systemtap at sourceware dot org
- Date: Wed, 05 Jun 2013 01:20:16 +0000
- Subject: [Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order
- Auto-submitted: auto-generated
http://sourceware.org/bugzilla/show_bug.cgi?id=15575
Bug ID: 15575
Summary: __tcp_sock_dport and __tcp_sock_sport should return
host order
Product: systemtap
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: tapsets
Assignee: systemtap at sourceware dot org
Reporter: jistone at redhat dot com
The tapset functions __tcp_sock_dport and __tcp_sock_sport are returning their
respective values as-is, which happens to be network order. This is confusing
for users; we ought to present host order instead. This will also parallel the
similar skb functions that already do ntohs().
Reported-by: "bcall" on freenode #systemtap
--
You are receiving this mail because:
You are the assignee for the bug.