quoted
I assume you are talking about collision with userspace. These
definitions are already protected by #ifdef __KERNEL__.
That should be enough to protect against collisions with
userspace I think.
Within the kernel he means, please put a TCP_* prefix onto these
values.
Given the values are currently:
quoted
+#define SACK_SEEN (1 << 0) /*1 = peer is SACK capable, */
+#define FACK_ENABLED (1 << 1) /*1 = FACK is enabled locally*/
+#define DSACK_SEEN (1 << 2) /*1 = DSACK was received from
peer*/
But the structure field member is 'sack_ok', unless it generates
very silly long lines - which in this case it probably doesn't -
it might even be worth prefixing with TCP_SACK_OK_ although
that might be deemed excessive!
David