Re: [PATCH RFC v3 1/8] vsock: expose the core port allocator to transports

[sashiko-bot@kernel.org]

> The core port allocator is currently private to connection-oriented
> sockets. Virtio datagrams need the core bound table and port allocation,
> while VMCI datagrams must keep their own endpoint creation and port
> namespace.
> 
> Export vsock_bind_common() with the bound-table locking inside the
> helper, and use it for stream and SEQPACKET binds. Keep datagram binds
> delegated to the transport so a transport can opt into the core
> allocator without changing other transports' binding behavior.
> 
> Keep datagram and connection-oriented sockets in separate logical port
> spaces within the core bound table. Filter bind conflicts and bound-socket
> lookups by class, including wildcard CIDs and automatic port allocation,
> so datagram and stream/SEQPACKET sockets can share a CID and port. Stream
> and SEQPACKET sockets continue to conflict with each other.
> 
> Signed-off-by: Sergio Lopez <slp@redhat.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261113-vsock-dgram-support-v3-0-1523c8e9b27e@redhat.com?part=1