proc_create_net_data_write(9)

💅 proc_create_net_data_write(9) — a Kernel API Manual kiki ✨

okay bestie, welcome to the Kernel API Manual corner of the kernel. this page is about proc_create_net_data_write, and it's giving “make me a writable proc file that's net_ns-specific” energy. let's get into it 💖

🌸 NAME 🌸

proc_create_net_data_write — create a writable net_ns-specific proc file, periodt. 💅

✨ SYNOPSIS ✨

struct proc_dir_entry * proc_create_net_data_write (const char *name ,
       umode_t mode , struct proc_dir_entry *parent , const struct
       seq_operations *ops , proc_write_t write , unsigned int state_size ,
       void *data );

🎀 ARGUMENTS 🎀

• name — the name of the file. like its whole label, no cap.
• mode — the file's access mode. the mode bits vibe, iykyk.
• parent — the parent directory in which to create. where the file lives.
• ops — the seq_file ops with which to read the file. these do the reading magic.
• write — the write method with which to 'modify' the file. yes, 'modify' in quotes.
• state_size — the size of the per-file private state to allocate. allocate that private state, bestie.
• data — data for retrieval by pde_data. it's giving payload.

🦋 DESCRIPTION 🦋

okay so the whole point: create a network namespaced proc file in the parent directory, with the specified name and mode. it allows reading of a file that displays a series of elements, and it also provides for the file accepting writes that have some arbitrary effect. main character behavior, honestly.

the functions in the ops table are used to iterate over items to be presented and extract the readable content using the seq_file interface. that's the reading pipeline, slay.

the write function is called with the data copied into a kernel space scratch buffer and has a NUL appended for convenience. the buffer may be modified by the write function. write should return 0 on success. that's the success vibe check: 0.

the data value is accessible from the show and write functions by calling pde_data on the file inode. and the network namespace must be accessed by calling seq_file_net on the seq_file struct. not optional, bestie — that's the rule.

🌈 SEE ALSO 🌈

• Kernel file ./fs/proc/proc_net.c — go peek, iykyk 👀
• proc_create_net_single_write(9) — also on the SEE ALSO list, go say hi 🫶

💌 and that's a wrap! source/version: ./fs/proc · date: October 2026 · page: proc_create_net_data_write(9) · mwah, bye bestie 💋