alloc_max_bench_buffer(9)

✨ alloc_max_bench_buffer(9) ✨

okay so bestie, welcome to the Kernel API Manual — yes we're doing kernel internals today and yes you're gonna slay it 💅 this one's a KUnit helper, which is basically the kernel's own little testing bestie, and it does exactly one job: grab you a buffer big enough for the fattest test case you've got. no cap, that's the whole vibe.

---

🎀 NAME 🎀

alloc_max_bench_buffer — allocate a buffer sized for the maximum test case. periodt.

---

🦋 SYNOPSIS 🦋

void * alloc_max_bench_buffer (struct kunit *test , const size_t *lens ,
       size_t count , size_t *buf_len );

---

🌸 ARGUMENTS 🌸

• test — the KUnit context, aka the main character that keeps track of the allocation for you (managed allocation, so it gets cleaned up, we love an organized icon 👑).
• lens — an array of lengths, literally the lengths used across the benchmark cases. hand it over and it'll find the biggest one.
• count — how many elements are chilling in that lens array. (not me needing the count, but okay, valid, lens doesn't carry its own size 🙈)
• buf_len — [out] parameter, bestie! pointer where the actually allocated buffer size gets stored — and yes, that size includes the NUL character 💀 don't forget the NUL, she counts.

---

🌈 RETURN 🌈

A pointer to the allocated memory ✨ … or NULL on failure 😭 (in which case, vibe check failed, handle it).

---

🧚 SEE ALSO 🧚

• Kernel file ./lib/tests/string_kunit.c
• strscpy_check(9)
• fill_random_string(9)
• STRING_BENCH(9)
• STRING_BENCH_BUF(9)

go read those too, they're all part of the same friend group 🫶

---

and that's the page, bestie 💖 this little masterpiece lives in ./lib/tests, dropped October 2026, and it's section 9 energy all the way — alloc_max_bench_buffer(9), iconic, no notes 🎀⭐🔥