seq_path(9)
π
seq_path β like, the seq_file glow-up for pathnames, bestie
okay so this is seq_path, and it lives in the Kernel API Manual (section 9, obvi), and it's literally the seq_file interface whose whole personality is printing a pathname. she's a little function with big main character energy π
β¨ NAME β¨
seq_path β the seq_file interface to print a pathname. that's it, that's the vibe. π¦
πΈ SYNOPSIS πΈ
int seq_path (struct seq_file *m , const struct path *path , const char *esc );
like, three args, one int coming back at you. no cap. β¨
π ARGUMENTS π
mβ theseq_filehandle. your little output bestie, she holds the whole thing together π«Άpathβ thestruct pathto print. the actual path-ness you're serving πescβ set of characters to escape in the output. give her the escape list and she'll handle it, iykyk π
π DESCRIPTION π
so the function returns the absolute path of 'path' β and that path is exactly what's represented by the dentry / mnt pair inside the path parameter π§
like, dentry + mnt = the path, and seq_path puts it out there for you. iconic behaviour, honestly. π₯
π¦ SEE ALSO π¦
kernel file ./fs/seq_file.c and literally the whole seq-iverse, because she runs with a crowd:
seq_open(9)seq_read(9)seq_lseek(9)seq_release(9)seq_escape_mem(9)seq_mangle_path(9)seq_file_path(9)seq_put_decimal_ull_width(9)seq_put_hex_ll(9)seq_write(9)seq_pad(9)seq_hlist_start(9)seq_hlist_start_head(9)seq_hlist_next(9)seq_hlist_start_rcu(9)seq_hlist_start_head_rcu(9)seq_hlist_next_rcu(9)seq_hlist_start_percpu(9)seq_hlist_next_percpu(9)
okay that's the whole page, mwah π this one's from ./fs, dated October 2026, and she's page seq_path(9) β go off, kernel docs, you ate πβ
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms