Jakub Sitnicki wrote: > Tooling that populates the SOCKMAP with sockets from user-space needs a way > to inspect its contents. Returning the struct sock * that SOCKMAP holds to > user-space is neither safe nor useful. An approach established by > REUSEPORT_SOCKARRAY is to return a socket cookie (a unique identifier) > instead. > > Since socket cookies are u64 values SOCKMAP needs to support such a value > size for lookup to be possible. This requires special handling on update, > though. Attempts to do a lookup on SOCKMAP holding u32 values will be met > with ENOSPC error. > > Signed-off-by: Jakub Sitnicki <jakub@xxxxxxxxxxxxxx> > --- Acked-by: John Fastabend <john.fastabend@xxxxxxxxx>
