SBPF Static Syscalls

Summary

This SIMD introduces static syscalls, using the eBPF call instruction encoding, to remove runtime relocations while keeping compatibility with the eBPF encoding.

Motivation

The resolution of syscalls during ELF loading requires relocating addresses, which is a performance burden for the validator. Relocations require an entire copy of the ELF file in memory to either relocate addresses we fetch from the symbol table or offset addresses to after the start of the virtual machine's memory. Moreover, relocations pose security concerns, as they allow the arbitrary modification of program headers and programs sections. Introducing static syscalls allows us to resolve all program relocations during link time.

Dependencies

This proposal depends on the following previously accepted proposal:

• SIMD-0189: SBPF stricter ELF headers

  Deprecation of PT_DYNAMIC header for SBPFv3 programs

New Terminology

None.

Detailed Design

The following must go into effect if and only if a program indicates the SBPF version 0x03 or higher in its ELF header e_flags field, according to the specification of SIMD-0161.

Static syscall instruction

We follow the encoding referenced in the eBPF specification for encoding static syscalls. That means we must use the call instruction (opcode 0x85) with the source register field set to zero. The immediate field must be filled with a registered syscall hash code. For more reference on the SBF ISA format, see the spec document.

We define the hash code for a syscall as the murmur32 hash of its respective name. The 32-bit immediate value of the call instruction must be the integer representation of such a hash. For instance, the code for abort is given by murmur32("abort"), so the instruction hexadecimal representation should look like 85 00 00 00 11 1a fc b6.

Consequently, system calls in the Solana SDK and in any related compiler tools must be registered as function pointers, whose address is the murmur32 hash of their name.

This new instruction comes together with modifications in the semantics of the instruction opcode 0x85 with source register set to one, which must only refer to internal calls and its immediate field must only be interpreted as a relative address to jump from the program counter.

As static syscalls don't use dynamic text-based relocations, the PT_DYNAMIC program header, along with the .dynamic, .dynsym, .dynstr and .rel.dyn section header entries will no longer be required to invoke static syscalls for any SBPFv3 program and will be omitted by default.

Albeit rare, hash collisions may occur depending on the syscall name, so care must be taken not to introduce names whose hash collides with existing ones. We expect core developers to rely on proper testing to identify such cases when registering a new syscall in the program loader. It is worth pointing that the solution proposed in this document is an improvement over the existing mechanism that does not realiably distinguish internal and external calls.

Alternatives Considered

None.

Impact

The changes proposed in this SIMD are transparent to dApp developers. The compiler toolchain will emit correct code for the specified SBF version. Static syscalls obviate relocations for call instructions and move the virtual machine closer to eliminating relocations altogether, which can bring considerable performance improvements.

Security Considerations

None.