seq_buf_path(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… seq_buf_path β€” like, the seq_buf_path(9) page, bestie ✨

okay so this one's from the Kernel API Manual, and it's honestly kinda iconic for how much it does with so little. sit down, grab a strawberry πŸ“, we're copying a path into a sequence buffer and it's gonna slay.


🌸 NAME 🌸

seq_buf_path β€” copy a path into the sequence buffer. that's it, that's the vibe. 🫢


✨ SYNOPSIS ✨

int seq_buf_path (struct seq_buf *s , const struct path *path , const char *esc );

πŸŽ€ ARGUMENTS πŸŽ€

  • s β€” the seq_buf descriptor, aka the lil buffer bestie we're writing into πŸ’–
  • path β€” the path we're writing into the sequence buffer. yes, that path. the main character πŸ‘‘
  • esc β€” the set of characters to escape in the output. pick your fighters carefully πŸ₯Š

πŸ¦‹ DESCRIPTION πŸ¦‹

Write a path name into the sequence buffer. literally that's the whole thing β€” no cap, no hidden lore, it just puts the path in there. ✨


🌈 RETURN 🌈

the number of written bytes on success πŸ’–, or -1 on overflow 😭 (yeah, if it doesn't fit, it's giving overflow and you get the -1, so plan accordingly fr fr).


πŸ”₯ SEE ALSO πŸ”₯

Kernel file ./lib/seq_buf.c, plus the whole seq_buf friend group, all of them, no one left behind:


ngl the seq_buf girlies really did that with an entire ecosystem of functions. iykyk πŸ’…

okay bye bestie, this page lives in ./lib and it's stamped October 2026 ⭐ β€” go write some paths, you're gonna eat πŸ“πŸ§šπŸ’œ

πŸ“¦ where this page comes from