On 11/19/18 11:36 AM, Joe Stringer wrote: > Hi David, thanks for pointing this out. > > This is more of an oversight through iterations, the runtime lookup > will fail to find a socket if the netns value is greater than the > range of a uint32 so I think it would actually make more sense to drop > the parameter size to u32 rather than u64 so that this would be > validated at load time rather than silently returning NULL because of > a bad parameter.
ok. I was wondering if it was a u64 to handle nsid of 0 which as I understand it is a legal nsid. If you drop to u32, how do you know when nsid has been set? > > I'll send a patch to bpf tree. > ok.
