Messages in this thread | | | From | David Laight <> | Subject | RE: remove kernel_setsockopt and kernel_getsockopt | Date | Thu, 14 May 2020 10:26:41 +0000 |
| |
From: Christoph Hellwig > Only for those were we have users, and all those are covered.
What do we tell all our users when our kernel SCTP code no longer works?
It uses SO_REUSADDR, SCTP_EVENTS, SCTP_NODELAY, SCTP_STATUS, SCTP_INITMSG, IPV6_ONLY, SCTP_SOCKOPT_BINDX_ADD and SO_LINGER. We should probably use the CONNECTX function as well.
I doubt we are the one company with out-of-tree drivers that use the kernel_socket interface.
David
- Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK Registration No: 1397386 (Wales)
| |