From: Neil Horman ... > > No there is not direct overlap between the two. However, as Michael pointed out, > > there is a new option to control SCTP_RCVINFO. So would could add a deprecation > > warning to the over SCTP_EVENTS option and carry SCTP_SNDRCVINFO with it. > > Once SCTP_EVENTS goes away so can SCTP_SNDRCVINFO. > > > Ok, so we should still consider deprecation warnings then. Daniel, what about > ratelimited warnings with pids included then? Can you defer any deprecation warnings for a few kernel versions? This gives time for applications to be recoded. Including argv[0] (even just the exec-time value) is much more use than the pid. Actually this is 'right PITA' for an application. A program binary that needs to work with old and new kernels will have to try the new option, and if it fails fall back to the old one, and then conditionally create/inspect the cmsg data. I can't actually imagine anyone bothering! Our sctp code is actually in a kernel module, so we can look at the kernel version when (part of) the driver is compiled on the target system. David -- To unsubscribe from this list: send the line "unsubscribe linux-sctp" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
