I am additionally wondering how the FUSE read/write operations interact with the generic routines for block i/o in the kernel?
As I understand it for a normal native file system, like ext2 or something, a write might not actually go to disk, but is instead ending
up being buffered by the block I/O layer, until some flushing daemon comes along or someone calls the sync() style functions.

How does fuse work in this respect? Any risc of these things happening, or will all read/write requests always be forwarded to the
FUSE lib, never "getting caught" in the page cache of the kernel?