chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>What is wrong with your idea of updatesockopt(2) ? Or maybe call it
>>getsockopt2() and only use it for the "get with extra argument" case.
>
>I guess
In article ,
Robert Swindells wrote:
>
>What is wrong with your idea of updatesockopt(2) ? Or maybe call it
>getsockopt2() and only use it for the "get with extra argument" case.
I guess getsockopt2/updatesockopt is not that bad after all. Perhaps
David Holland wrote:
>On Mon, Dec 18, 2017 at 07:21:33PM +, David Holland wrote:
> > On Thu, Dec 07, 2017 at 03:04:32PM +, Robert Swindells wrote:
> > > I wrote:
> > >> Does anyone know why we don't use the input 'optlen' parameter to the
> > >> getsockopt(2)
On Mon, Dec 18, 2017 at 07:21:33PM +, David Holland wrote:
> On Thu, Dec 07, 2017 at 03:04:32PM +, Robert Swindells wrote:
> > I wrote:
> >> Does anyone know why we don't use the input 'optlen' parameter to the
> >> getsockopt(2) syscall, we do write back to it on return.
> >>
On Thu, Dec 07, 2017 at 03:04:32PM +, Robert Swindells wrote:
> I wrote:
>> Does anyone know why we don't use the input 'optlen' parameter to the
>> getsockopt(2) syscall, we do write back to it on return.
>> [...]
>>
>> There are also lots of places in sctp_usrreq that want to use it.
In article ,
Robert Swindells wrote:
>
>There are about 40 options defined by SCTP. I would need to go through
>the list to see how many of them were of which type.
>
>There isn't any source shared between FreeBSD and NetBSD anymore, their
>stack
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>Options for NetBSD:
>>
>> Copy in optval for getsockopt(2):
>>
>>Pro: Allows "get" of IP_IPSEC_POLICY using original KAME API.
>>Con: Diverges from
In article ,
Robert Swindells wrote:
>
>chris...@astron.com (Christos Zoulas) wrote:
>>In article ,
>>Robert Swindells wrote:
>>>
>>>chris...@astron.com (Christos Zoulas) wrote:
In article
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>chris...@astron.com (Christos Zoulas) wrote:
>>>In article ,
>>>Robert Swindells wrote:
In article ,
Robert Swindells wrote:
>
>chris...@astron.com (Christos Zoulas) wrote:
>>In article ,
>>Robert Swindells wrote:
>>>
>>>chris...@astron.com (Christos Zoulas) wrote:
In article
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>chris...@astron.com (Christos Zoulas) wrote:
>>>In article ,
>>>
>>>So depending on the contents of the sockval we do something
In article ,
Robert Swindells wrote:
>
>chris...@astron.com (Christos Zoulas) wrote:
>>In article ,
>>
>>So depending on the contents of the sockval we do something different?
>
>FreeBSD does. The calls to copy in or
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>I wrote:
>>>Does anyone know why we don't use the input 'optlen' parameter to the
>>>getsockopt(2) syscall, we do write back to it on return.
>>>
>>>In
In article ,
Robert Swindells wrote:
>
>I wrote:
>>Does anyone know why we don't use the input 'optlen' parameter to the
>>getsockopt(2) syscall, we do write back to it on return.
>>
>>In ip_output() there is this, which suggests that someone had
I wrote:
>Does anyone know why we don't use the input 'optlen' parameter to the
>getsockopt(2) syscall, we do write back to it on return.
>
>In ip_output() there is this, which suggests that someone had come
>across this before.
>
>#if 0 /* defined(IPSEC) */
>case
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>chris...@astron.com (Christos Zoulas) wrote:
>>>In article ,
>>>Robert Swindells wrote:
I wrote:
In article ,
Robert Swindells wrote:
>
>chris...@astron.com (Christos Zoulas) wrote:
>>In article ,
>>Robert Swindells wrote:
>>>
>>>I wrote:
Does anyone know why we don't use the input 'optlen'
chris...@astron.com (Christos Zoulas) wrote:
>In article ,
>Robert Swindells wrote:
>>
>>I wrote:
>>>Does anyone know why we don't use the input 'optlen' parameter to the
>>>getsockopt(2) syscall, we do write back to it on return.
[snip]
In article ,
Robert Swindells wrote:
>
>I wrote:
>>Does anyone know why we don't use the input 'optlen' parameter to the
>>getsockopt(2) syscall, we do write back to it on return.
>>
>>In ip_output() there is this, which suggests that someone had
I wrote:
>Does anyone know why we don't use the input 'optlen' parameter to the
>getsockopt(2) syscall, we do write back to it on return.
>
>In ip_output() there is this, which suggests that someone had come
>across this before.
>
>#if 0 /* defined(IPSEC) */
>case
20 matches
Mail list logo