instrument_memcpy_after(9)

💅 instrument_memcpy_after(9) 💅

okay so bestie, we’re in the Kernel API Manual, and this page is all about that post-memcpy instrumentation glow-up ✨

---

✨ NAME ✨

instrument_memcpy_after — add instrumentation after a non-instrumented memcpy 💖

---

🌸 SYNOPSIS 🌸

void instrument_memcpy_after (void *to , const void *from , unsigned long n , unsigned long left );

---

🎀 ARGUMENTS 🎀

• to — the destination address 🎯
• from — the source address 🫶
• n — number of bytes to copy 🌈
• left — number of bytes not copied, if known 👀

---

🦋 DESCRIPTION 🦋

okay so this is for instrumenting memory accesses that happen inside custom memcpy implementations 💅. The instrumentation should be inserted after the memcpy call — that’s the whole vibe of this one, bestie ✨

---

💖 SEE ALSO 💖

Kernel file ./include/linux/instrumented.h plus all these iconic little functions:

• instrument_read(9)
• instrument_write(9)
• instrument_read_write(9)
• instrument_atomic_read(9)
• instrument_atomic_write(9)
• instrument_atomic_read_write(9)
• instrument_copy_to_user(9)
• instrument_copy_from_user_before(9)
• instrument_copy_from_user_after(9)
• instrument_memcpy_before(9)
• instrument_get_user(9)
• instrument_put_user(9)

---

cute little sign-off: this page’s source/version is ./include/linux and it’s dated October 2026 🎀💜