[Bugs] [Bug 1630804] libgfapi-python: test_listdir_with_stat and test_scandir failure on release 5 branch

bugzilla at redhat.com bugzilla at redhat.com
Fri Oct 12 04:46:29 UTC 2018


Raghavendra G <rgowdapp at redhat.com> changed:

           What    |Removed                     |Added
                 CC|                            |skoduri at redhat.com
              Flags|                            |needinfo?(skoduri at redhat.co
                   |                            |m)

--- Comment #9 from Raghavendra G <rgowdapp at redhat.com> ---
Following is the likely hypothesis:

* readdir-ahead on seeing a write invalidates "attribute" (rest of iatt other
than gfid and ia_type) information keeping "entry" (gfid, ia_type) information,
by zeroing out the iatt corresponding to "attribute" part of iatt.
* Fuse-bridge if it sees zeroed out attribute information, sets
attribute_valid=0 to indicate kernel to consume only entry information and
asking it to do explicit stats for attribute information.

However, on gfapi this option of selectively sending entry information may not
be available and hence the entire iatt is to be invalidated and no inode
information returned (just like readdir).


How does gfapi handle dentries with zeroed out stats? What information does it
send back to application?

You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.

More information about the Bugs mailing list