Displaying 5 results from an estimated 5 matches for "1202235".
2020 Apr 27
4
[PATCH net-next 0/3] vsock: support network namespace
...;netns' module param to vsock.ko to enable the
> network namespace support (disabled by default)
> * added 'vsock_net_eq()' to check the "net" assigned to a socket
> only when 'netns' support is enabled
>
> RFC: https://patchwork.ozlabs.org/cover/1202235/
>
> Now that we have multi-transport upstream, I started to take a look to
> support network namespace in vsock.
>
> As we partially discussed in the multi-transport proposal [1], it could
> be nice to support network namespace in vsock to reach the following
> goals:
> -...
2020 Apr 27
4
[PATCH net-next 0/3] vsock: support network namespace
...;netns' module param to vsock.ko to enable the
> network namespace support (disabled by default)
> * added 'vsock_net_eq()' to check the "net" assigned to a socket
> only when 'netns' support is enabled
>
> RFC: https://patchwork.ozlabs.org/cover/1202235/
>
> Now that we have multi-transport upstream, I started to take a look to
> support network namespace in vsock.
>
> As we partially discussed in the multi-transport proposal [1], it could
> be nice to support network namespace in vsock to reach the following
> goals:
> -...
2020 Apr 27
0
[PATCH net-next 0/3] vsock: support network namespace
...to vsock.ko to enable the
> > network namespace support (disabled by default)
> > * added 'vsock_net_eq()' to check the "net" assigned to a socket
> > only when 'netns' support is enabled
> >
> > RFC: https://patchwork.ozlabs.org/cover/1202235/
> >
> > Now that we have multi-transport upstream, I started to take a look to
> > support network namespace in vsock.
> >
> > As we partially discussed in the multi-transport proposal [1], it could
> > be nice to support network namespace in vsock to reach th...
2020 Apr 28
0
[PATCH net-next 0/3] vsock: support network namespace
...am to vsock.ko to enable the
>> network namespace support (disabled by default)
>> * added 'vsock_net_eq()' to check the "net" assigned to a socket
>> only when 'netns' support is enabled
>>
>> RFC: https://patchwork.ozlabs.org/cover/1202235/
>>
>> Now that we have multi-transport upstream, I started to take a look to
>> support network namespace in vsock.
>>
>> As we partially discussed in the multi-transport proposal [1], it could
>> be nice to support network namespace in vsock to reach the follow...
2018 May 13
2
ACL set in Windows not set in Samba
Setup: Samba AD DC and Samba AD Member Server, Win10 clients only. Samba
version 4.8.1
Has something changed recently in the way ACL's are supposed to work? My
existing shares work just fine but any ALC changes I make using Windows are
ignored in Samba.
For example, I'm creating a new folder in Windows inside an existing share
and I add user User1 or group Group1 in the security tab.