STRUCT SECCOMP_DATA(9)
β¨ struct seccomp_data(9) β¨
okay so this is a page from the Kernel API Manual, and honestly? it's a little baddie. it's the struct that describes the format your BPF program executes over when seccomp is out here doing its thing. let's get into it π
πΈ NAME πΈ
struct seccomp_data β the format the BPF program executes over. that's it, that's the whole vibe. β¨
π¦ SYNOPSIS π¦
struct seccomp_data {
int nr;
__u32 arch;
__u64 instruction_pointer;
__u64 args[6];
};
like, look at her. so clean. so structured. main character energy fr fr π
π Members π
time to meet the cast, bestie. every field gets its moment π
nrβ the system call number. iconic, essential, the whole reason we're here π«Άarchβ indicates the system call convention as anAUDIT_ARCH_*value, as defined in<linux/audit.h>. yes bestie you literally need that header, no cap.instruction_pointerβ at the time of the system call. that's when. that's the moment. timestamped by the kernel herself πargsβ up to 6 system call arguments, always stored as 64-bit values regardless of the architecture. the way she doesn't care what arch you're on and keeps everything 64-bit anyway?? consistent queen. always 64-bit. periodt. π
ngl the "always stored as 64-bit values regardless of the architecture" part is the detail people forget, so like... don't forget it π
π SEE ALSO π
- Kernel file
./tools/include/uapi/linux/seccomp.hstruct seccomp_notif_addfd(9)
go read those too, iykyk. tag yourself, i'm the struct in the tools include directory π
and that's the page, bestie!! source is ./tools/include/uapi/linux, dated October 2026 β so like, future girlboss energy β love that for us. mwah, go write some slay BPF filters ππ§ββοΈπ₯
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms