ecryptfs_write_end(9)

💅 NAME 💅

ecryptfs_write_end — the grand finale of a write operation on an eCryptfs file (bestie, the manpage literally gives us no blurb here, so that's the whole vibe 😭)

✨ SYNOPSIS ✨

int ecryptfs_write_end (const struct kiocb *iocb , struct address_space
*mapping , loff_t pos , unsigned len , unsigned copied , struct folio
*folio , void *fsdata );

🎀 ARGUMENTS 🎀

Ok so here's the cast of characters, seven of them, no skipping 🫶

• iocb — the I/O control block for the eCryptfs file. it's the const struct kiocb * of the situation, main character energy fr.
• mapping — the eCryptfs object, struct address_space *mapping style.
• pos — the file position, a loff_t pos. yes queen, we know where we are.
• len — the length of the data. the manpage is like "unused" about this one 💀 so it's just vibing there.
• copied — the amount of data copied, unsigned copied. slay, that's the actual number we care about.
• folio — the eCryptfs folio, struct folio *folio. iconic memory container, no notes.
• fsdata — the fsdata, void *fsdata. also marked unused, so it's giving background extra 🙈.

🦋 SEE ALSO 🦋

• Kernel file ./fs/ecryptfs/mmap.c — go read the source, iykyk.
• ecryptfs_copy_up_encrypted_with_header(9)
• ecryptfs_read_folio(9)
• ecryptfs_write_begin(9) — the prequel to this whole saga, obviously 🔥

and that's the whole page bestie, we literally ate and left zero crumbs 💅✨ this lil slice of kernel API pain lives in ./fs/ecryptfs, dated October 2026, and the page itself is ecryptfs_write_end(9) — mwah, go forth and end some writes 🧚💜