Re: [PATCH net-next 1/5] sctp: Bring SCTP_MAXSEG socket option into ietf API extension compliance
From: David Miller <davem@davemloft.net>
Date: 2008-12-26 00:56:23
Also in:
linux-sctp
From: David Miller <davem@davemloft.net>
Date: 2008-12-26 00:56:23
Also in:
linux-sctp
From: Vlad Yasevich <redacted> Date: Fri, 19 Dec 2008 20:47:48 -0500
From: Wei Yongjun <redacted> Brings maxseg socket option set/get into line with the latest ietf socket extensions API draft, while maintaining backwards compatibility. Signed-off-by: Wei Yongjun <redacted> Signed-off-by: Vlad Yasevich <redacted>
Applied. But I really dislike this scheme used by the compat code. Half-way initializing a structure and then depending upon the logic in the rest of the function to make sure the rest of the struct (the uninitialized part) is never accessed? Give me a break, programming, auditing, and bug fixing is hard enough as it is without sloppy code like this.