Etienne Perot 80ee2d3acc Move max syscall number out of kernel package. ...

Also add "num" at the end of it so make it clear that it's an *inclusive*
limit. Fix the uses of it which didn't treat it as inclusive.

No strong opinion on where it should go, but having it available in
other places of the codebase is helpful. It's already in two places,
and I'd like to have it available in two more places:

 - In the seccomp program compiler, so that it knows how many syscalls
   it should check for deterministic-ness and caching the results.
 - In the seccomp fuzzer, to build an initial syscall corpus.

PiperOrigin-RevId: 576660986

2023-10-25 15:22:54 -07:00

..

BUILD

Move max syscall number out of kernel package.

2023-10-25 15:22:54 -07:00

sentry.go

Move max syscall number out of kernel package.

2023-10-25 15:22:54 -07:00

syscall.go

Move max syscall number out of kernel package.

2023-10-25 15:22:54 -07:00