Closed rogersimmons closed 2 years ago
OK if you say so, but we still need to pick a correct syscall number per architecture, or ensure we only allow mlock2 on AMD64.
The number 284 seems to be coming from uapi/asm-generic
- I'm not sure what it stands for given my limited experience with kernel.
However, I have checked out Linux v3.10
on which our agents are based, there are no mentions on mlock2, so it seems we can't run tests against this functionality on our agents.
As mentioned earlier the dev11/12/13 hosts have mlock2, it's just not exposed via glibc:
$> man mlock2
Note: currently, there is not a glibc wrapper for mlock2(), so it will need to be invoked using syscall(2).
mlock2 functionality exists in kernels before 4.4 - and in particular 3.x which dev# are using. The feature hasn't been wrapped in glibc which is why it hasn't been exposed. syscall can be used to access instead