[🔍]
$whoami

I spend an unhealthy amount of time below the abstraction layer—watching user space, operating system kernels, and computer architecture passively-aggressively disagree about what the code was supposed to do.

~/.profile

DEGREE: B.S. Computer Engineering
FOCUS: Computer Systems Security
TARGETS: Linux / macOS — x86_64, ARM64
DEBUGGING: Blaming the compiler first (gcc -O0)

What I Do

I write low-level C and assembly, poke at privilege and memory boundaries, and study how operating systems and hardware behave under adversarial conditions. Most of my time goes to OS internals, memory mechanics, and computer architecture—with generous detours spent staring at a hex dump, trying to prove a crash is an undocumented CPU erratum and definitely not an off-by-one error I wrote twenty minutes ago.

Approach

Specifications are mostly optimistic fan fiction. The datasheet swears a boundary is airtight; the kernel mutters “usually, unless something races”; and the CPU speculatively executes right past the bounds check anyway just to see what is on the other side. I prefer verifying assumptions directly on live kernels and bare metal, because emulators lie, documentation forgets, and “that should never happen” is basically a formal invitation to write a PoC.

cat /proc/self/skills
  • C / C++ & Assembly (ARM64, x86_64) — survivor of undefined behavior
  • OS Internals, Virtual Memory & Kernel Boundaries — poking(fuzzing) them to see what falls out
  • Hardware & Microarchitectural Security — trusting nothing that runs faster than it should
  • GPU / Compute Backends (Metal, CUDA, OpenCL — yes, all three; send help)

About This Log

MADV_DONTNEED is a technical notebook for computer systems security, OS internals, and low-level experiments—named after the Linux “advice” flag that politely hears your suggestion and immediately vaporizes your pages anyway, much like -O3 does to a plain memset().