netfs_unbuf..._iter_locked(9)

💖 netfs_unbuf..._iter_locked(9) 💖

okay bestie, this is the manual page for netfs_unbuf..._iter_locked(9) from the Kernel API Manual, and it’s giving “locked, direct, no pagecache” energy. Let’s get into it. 🫶

✨ NAME ✨

netfs_unbuffered_read_iter_locked — Perform an unbuffered or direct I/O read

🦋 SYNOPSIS 🦋

ssize_t netfs_unbuffered_read_iter_locked (struct kiocb *iocb , struct
iov_iter *iter );

🎀 ARGUMENTS 🎀

• iocb — The I/O control descriptor describing the read. It’s literally the main character of this read operation 💅
• iter — The output buffer (also specifies read length). Yes, it’s both the destination and the length info, iconic.

🌸 DESCRIPTION 🌸

Perform an unbuffered I/O or direct I/O from the file in iocb to the output buffer. No use is made of the pagecache. Not a single pagecache vibe. 💀

The caller must hold any appropriate locks. That’s a must, bestie — the “locked” in the name is not decorative. 🔒

Locking check: the caller must hold any appropriate locks. No cap. ⚠️

🔥 SEE ALSO 🔥

• Kernel file ./fs/netfs/direct_read.c
• netfs_unbuffered_read_iter(9)

xoxo, bestie 🫶 this page comes from ./fs/netfs, dated October 2026, and it lives in the Kernel API Manual. slay and stay locked 💅✨