strscpy_check(9)

💅 strscpy_check(9) 💅

okay so this is from the Kernel API Manual, bestie, and we're looking at strscpy_check(9) — a specific test case runner with tiny helper main character energy 🎀

---

✨ NAME ✨

strscpy_check — run a specific test case. periodt 💖

---

🧪 SYNOPSIS 🧪

void strscpy_check (struct kunit *test , char *src , int count , int expected , int chars , int terminator , int pad );

---

🎀 ARGUMENTS 🎀

• test — KUnit test context pointer. it's the test's little backpack 🎒
• src — source string, and it's the argument you hand to strscpy_pad ✨
• count — size of the destination buffer, also an argument to strscpy_pad 📏
• expected — the return value you expect from the call to strscpy_pad 👀
• chars — number of characters from the src string that should get written to the dst buffer 💫
• terminator — 1 if there should be a terminating null byte, 0 otherwise 🫶
• pad — number of pad characters expected in the tail of the dst buffer. (pad does not include the null terminator byte.) 🧚

---

💖 DESCRIPTION 💖

It calls strscpy_pad and then verifies the return value and the state of the destination buffer after the call returns. lowkey a little post-call vibe check, but for real correctness 🔥

---

🌈 SEE ALSO 🌈

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

---

mwah 💋 — source/version is ./lib/tests, dated October 2026, and yeah bestie, that's the strscpy_check(9) page 🫶