New: SO_PRIORITY does not set TOS field in IP header
https://bugzilla.kernel.org/show_bug.cgi?id=35852
URL: http://www.kernel.org/doc/man-pages/online/pages/man7/
socket.7.html
Summary: SO_PRIORITY does not set TOS field in IP header
Product: Documentation
Version: unspecified
Kernel Version: n/a
Platform: All
OS/Version: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
AssignedTo: documentation_man-pages-ztI5WcYan/[email protected]
ReportedBy: [email protected]
Regression: No
The socket man page says that setsockopt with level=SOL_SOCKET and optname=SO_PRIORITY sets the TOS field in IP header:
http://www.kernel.org/doc/man-pages/online/pages/man7/socket.7.html
However, my experiments and other web search results suggest that the socket man page is wrong. SO_PRIORITY does not seem to set the TOS field in the IP header.
Signature · 7 lines
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 35852] SO_PRIORITY does not set TOS field in IP header
In reply to a message not in the archivehttps://bugzilla.kernel.org/show_bug.cgi?id=35852
[email protected] changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]
--- Comment #1 from [email protected] --- This bug is against a old man pages. Please check with a newer verison. Nick
Signature · 6 lines
You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 35852] SO_PRIORITY does not set TOS field in IP header
In reply to a message not in the archivehttps://bugzilla.kernel.org/show_bug.cgi?id=35852
Michael Kerrisk <[email protected]> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |[email protected]
Resolution|--- |CODE_FIX--- Comment #2 from Michael Kerrisk <[email protected]> --- (In reply to advaitdixit from comment #0)
Quoted 7 lines
The socket man page says that setsockopt with level=SOL_SOCKET and optname=SO_PRIORITY sets the TOS field in IP header:
http://www.kernel.org/doc/man-pages/online/pages/man7/socket.7.htmlHowever, my experiments and other web search results suggest that the socket man page is wrong.
SO_PRIORITYdoes not seem to set the TOS field in the IP header.
A quick scan of the kernel source also finds nothing to suggest that SO_PRIORITY sets the TOS field in the IP header.
Various URLs question this text in teh man page
http://mailman.isi.edu/pipermail/ns-developers/2012-September/010638.html
https://athena.ecs.csus.edu/~bransone/pub/misc/netfilter_notes/qos
https://ocrete.ca/2009/07/24/when-a-man-page-lies/
http://lkml.iu.edu/hypermail/linux/net/0512.3/0008.html
So, I'll remove this text from socket(7) (and also similar text in ip(7)), and close this bug.
Thanks.
Signature · 6 lines
You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
[Bug 35852] SO_PRIORITY does not set TOS field in IP header
In reply to a message not in the archivehttps://bugzilla.kernel.org/show_bug.cgi?id=35852
--- Comment #3 from Michael Kerrisk <[email protected]> --- And one more URL that questioned the effect of SO_PRIORITY on IP TOS:
http://thread.gmane.org/gmane.linux.man/2074
Signature · 6 lines
You are receiving this mail because: You are watching the assignee of the bug. -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html