seq_buf_str(9)

💅 seq_buf_str(9) — the kernel API manual, bestie edition

So you found your way into seq_buf_str(9) from the Kernel API Manual — welcome, this one's short and sweet and honestly kind of iconic. It's all about turning your lil seq_buf into a string you can actually trust. 🎀

---

✨ NAME ✨

seq_buf_str — get a NUL-terminated C string out of a seq_buf, no cap

---

🌸 SYNOPSIS 🌸

const char * seq_buf_str (struct seq_buf *s );

---

🦋 ARGUMENTS 🦋

• s — the seq_buf handle. that's it. that's the whole argument list. main character energy honestly 💅

---

🔥 DESCRIPTION 🔥

okay so here's the vibe: this call makes absolutely sure the buffer inside s is NUL-terminated and therefore safe to read as a string. slay. ✨

bestie, heads up 🙈 — if you call this when the buffer has overflowed, then the last byte of the buffer gets zeroed, and the len will still point past it. like, it's fine, but also… it's not fine, iykyk.

After this function has been called, s->buffer is safe to use in string operations. periodt. 🫶

---

⭐ RETURN ⭐

It returns s->buf — after making sure it's terminated, obviously. no crumbs. 👑

---

🌈 SEE ALSO 🌈

• Kernel file ./include/linux/seq_buf.h
• struct seq_buf(9)
• seq_buf_get_buf(9)
• seq_buf_commit(9)
• seq_buf_pop(9)

all of these are literally in the same friend group, go say hi 💖

---

that's the whole page, bestie — no cap, you ate that. this one's coming at you from ./include/linux, October 2026 edition, filed under seq_buf_str(9). go forth and terminate your strings properly 🧚💜