* [Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order @ 2013-06-05 1:20 jistone at redhat dot com 2013-06-05 1:27 ` [Bug tapsets/15575] " jistone at redhat dot com 2013-08-05 17:57 ` dsmith at redhat dot com 0 siblings, 2 replies; 3+ messages in thread From: jistone at redhat dot com @ 2013-06-05 1:20 UTC (permalink / raw) To: systemtap 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. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug tapsets/15575] __tcp_sock_dport and __tcp_sock_sport should return host order 2013-06-05 1:20 [Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order jistone at redhat dot com @ 2013-06-05 1:27 ` jistone at redhat dot com 2013-08-05 17:57 ` dsmith at redhat dot com 1 sibling, 0 replies; 3+ messages in thread From: jistone at redhat dot com @ 2013-06-05 1:27 UTC (permalink / raw) To: systemtap http://sourceware.org/bugzilla/show_bug.cgi?id=15575 Josh Stone <jistone at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Josh Stone <jistone at redhat dot com> --- commit db7b8b2ff97c6f532f5f2941ca25f1859a0fcdc8 -- You are receiving this mail because: You are the assignee for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug tapsets/15575] __tcp_sock_dport and __tcp_sock_sport should return host order 2013-06-05 1:20 [Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order jistone at redhat dot com 2013-06-05 1:27 ` [Bug tapsets/15575] " jistone at redhat dot com @ 2013-08-05 17:57 ` dsmith at redhat dot com 1 sibling, 0 replies; 3+ messages in thread From: dsmith at redhat dot com @ 2013-08-05 17:57 UTC (permalink / raw) To: systemtap http://sourceware.org/bugzilla/show_bug.cgi?id=15575 David Smith <dsmith at redhat dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dsmith at redhat dot com --- Comment #2 from David Smith <dsmith at redhat dot com> --- *** Bug 13702 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are the assignee for the bug. ^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2013-08-05 17:57 UTC | newest] Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed) -- links below jump to the message on this page -- 2013-06-05 1:20 [Bug tapsets/15575] New: __tcp_sock_dport and __tcp_sock_sport should return host order jistone at redhat dot com 2013-06-05 1:27 ` [Bug tapsets/15575] " jistone at redhat dot com 2013-08-05 17:57 ` dsmith at redhat dot com
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).