mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 05:16:00 +03:00
[PR #2736] [MERGED] Fixed negative stat cache data was not working #2755
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#2755
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/s3fs-fuse/s3fs-fuse/pull/2736
Author: @ggtakec
Created: 10/4/2025
Status: ✅ Merged
Merged: 10/9/2025
Merged by: @gaul
Base:
master← Head:fix/negative_cache📝 Commits (1)
9bddbdeFixed negative stat cache data was not working📊 Changes
1 file changed (+16 additions, -23 deletions)
View changed files
📝
src/s3fs.cpp(+16 -23)📄 Description
Relevant Issue (if applicable)
#2735
Details
This is a fix for issue #2735.
This was a bug introduced while modifying the PR #2707.
A negative cache check was overlooked.
This fix is consistent with the request count results examined in #2707 and has no impact on request count reduction, so there is no impact about request count.
(Compared to the code at
github.com/s3fs-fuse/s3fs-fuse@0448ff460b)Note that incorporating this bug into test code is difficult.
This is because the only way to determine whether a cache hit occurred and whether a subsequent request occurred is through logs.
Also, this would require multiple tests to check for non-existent objects, and would require detecting differences in their internal behavior.
Thanks to @francoisfreitag for his help.
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.