ima_queue_delete_partial(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ima_queue_delete_partial(9) πŸ’…

okay bestie, welcome to the Kernel API Manual ✨ β€” today's main character is ima_queue_delete_partial, and honestly? she's giving cleanup crew energy. πŸ§ΉπŸ’–


🌸 NAME 🌸

ima_queue_delete_partial β€” Delete current measurements πŸ—‘οΈβœ¨


πŸ¦‹ SYNOPSIS πŸ¦‹

int ima_queue_delete_partial (unsigned long req_value );

like, that's the whole signature. short and iconic. no notes. πŸ‘‘


πŸŽ€ ARGUMENTS πŸŽ€

  • req_value β€” Number of measurements to delete πŸ”’πŸ’€ that's how many of them are getting un-alived from the list, bestie.

πŸ’œ DESCRIPTION πŸ’œ

okay so here's what she does: she deletes the requested number of measurements from the current measurements list, and then updates the number of records and the binary run-time size accordingly. everything stays in sync, no cap. πŸ”₯

but here's the gag πŸ™ˆ β€” she will refuse to delete current measurements if measurement is suspended. and the reason is actually kind of genius, lowkey: it means the dump can be done in a lockless way πŸ’…, and user space gets notified that current measurements are being carried over to the secondary kernel, so it doesn't save them twice. imagine the double-save. the horror. 😭🫢


⭐ RETURN ⭐

Zero on success πŸŽ‰, a negative value otherwise πŸ’€. classic. slay.


🌈 SEE ALSO 🌈

go read the whole squad, iykyk πŸ‘‘πŸ’–


signed, sealed, delivered by ./security/integrity/ima πŸ’Œ β€” version vibes October 2026 πŸ—“οΈβœ¨, and yes this whole thing is still ima_queue_delete_partial(9) until the very last line, periodt. πŸ’…πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from