rproc_report_crash(9)

📦 version 7.3.1, in nixpkgs unstable

💅 rproc_report_crash(9) — like, the remoteproc crash reporter, bestie

okay so you're in the Kernel API Manual (section 9, the kernel-functions girlies) and this is the page for rproc_report_crash. she's short, she's iconic, she does exactly one thing, and honestly? she ate. let's get into it 🫶

✨ NAME ✨

rproc_report_crash — the rproc crash reporter function, no cap

🦋 SYNOPSIS 🦋

void rproc_report_crash (struct rproc *rproc , enum rproc_crash_type
type );

that's it. that's the whole signature. she's void, she's not returning anything to you, she's just doing the thing 💅

🎀 ARGUMENTS 🎀

  • rproc — the remote processor. the actual guy. the main character in question 🌸
  • type — the crash type (it's an enum rproc_crash_type, so you gotta tell her what kind of oopsie it was) 💀

🔥 DESCRIPTION 🔥

bestie listen, this is the important part. this function must be called every single time a crash is detected by the low-level drivers implementing a specific remoteproc. like, every time. not sometimes. not "when it's convenient." every time. periodt ✨

🚩 and no, do not call this from a non-remoteproc driver. it's not for you. it's not for your random driver. this is a remoteproc thing only, iykyk. stay in your lane, respectfully 🙈

the good news? she's flexible like that — this function can be called from atomic/interrupt context. so go off, call her from where you need to 🧚

👑 SEE ALSO 👑

Kernel file ./drivers/remoteproc/remoteproc_core.c — go read the source, it's giving required reading 📚

and the whole friend group, gathered here for the group chat (they all showed up, which is so sweet):

all thirty-three of them, in the order they appeared, because we do not skip anyone in this house 💖

anyway bestie, that's the page! it lives in ./drivers/remoteproc, it's from October 2026, and yes it lowkey slays. go report your crashes responsibly 🎀✨💜

📦 where this page comes from