Regarding FUSE GETARR and SETATTR Requests

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view

Regarding FUSE GETARR and SETATTR Requests

Bharath Kumar Reddy Vangoor
Hello All,

I’m trying to understand the flow of write back cache option in FUSE. I see in the function “fuse_write_iter” before calling “generic_file_write_iter”, there is a call to “fuse_update_attributes” which checks the time out on attributes and sends a “FUSE_GETATTR” to the user space. Upon receiving the attributes from user space it calls “fuse_change_attributes” which updates the inode attributes except “mtime” and “time” (in case of write back cache). And once the flush of dirty pages happen after “write_pages” there will be a call to “fuse_write_inode” which flushes the “mtime” and “ctime” to the user space using FUSE_SETATTR. My question here is which code is responsible for modifying the “mtime” and “ctime” of the anode inside the FUSE Kernel part that is sent to User space(in write back cache).

Any help is highly appreciated.


Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!;130105516;z
fuse-devel mailing list
To unsubscribe or subscribe, visit