Fixed data race about fuse_fill_dir_t function and data pointer #2214
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant Issue (if applicable)
#2213 #2212
Details
In the thread callback handler for
HeadRequest
called by FUSE readdir,void* buf
andfuse_fill_dir_t filler
seem not suitable for asynchronous writes.I checked the FUSE source code, but it seems that exclusive control for
buf
is not implemented byfiller
.s3fs
HeadRequests
are processed in parallel by multithreading, so it seems that thisfiller
call needs to be synchronized.However,
ThreadSanitizer
never detected this part yet.(Even if exclusive control is performed in the
filler
, I have decided that exclusive control on the s3fs side is not a particular problem, so I am submitting this PR.)This fix obsoletes
multi_head_callback_param
uses in threading functions and usesSyncFiller
objects instead.All data related to
filler
andbuf
are implemented inside theSyncFiller
object.(This includes
filled
variables added by #2212)SyncFiller
object handlesbuf
/filler
/filled
safely.