| | What happens if application is compiled with dccp_packet_info containing only | | one field (priority) and kernel containing two fields (for example priority | | and later added expiry time)? Wouldn't that implementation make extensions to | | dccp_packet_info impossible? | Had not looked at it from this point of view. So you are suggesting | | if (msg->msg_control != NULL && msg->msg_controllen >= sizeof(*dcp)) | dcp = (struct dccp_packet_info *)msg->msg_control; | | instead? Agreed, point #1 to change in the patch. | No, the above is nonsense. If the application uses an earlier version of the API, then it needs to be recompiled, there is no way it could pretend to have an adequate size. So my take is that still the '==' is correct. But maybe this is a known problem? The University of Aberdeen is a charity registered in Scotland, No SC013683. -- To unsubscribe from this list: send the line "unsubscribe dccp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
