mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 13:26:00 +03:00
[PR #1713] [MERGED] Prevents the etag string buffer from being destroyed during use #2134
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#2134
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/1713
Author: @ggtakec
Created: 7/3/2021
Status: ✅ Merged
Merged: 7/3/2021
Merged by: @gaul
Base:
master← Head:etag_stock📝 Commits (1)
0b2b7fbPrevents the etag string buffer from being destroyed during use📊 Changes
3 files changed (+20 additions, -24 deletions)
View changed files
📝
src/fdcache_fdinfo.cpp(+12 -5)📝
src/fdcache_fdinfo.h(+2 -18)📝
src/types.h(+6 -1)📄 Description
Relevant Issue (if applicable)
n/a
Details
There was a potential bug in the etag string saving process in parallel multipart uploads.
Currently, it has not been realized, but it may be a problem in future function addition(planned now), so it has been fixed.
This bug is the part that saves etag string when CURL processing is completed in parallel multipart upload.
The object has an etag as a pointer, but it is possible that the entity does not exist in the future.
Therefore, I added an
etag_entitiesmember to thePseudoFdInfoclass and modified it so that the etag entity always exists for the period when thePseudoFdInfoobject exists.And the
MPPART_INFOstructure has almost the same purpose and member variables as thefilepartstructure, so it is unified asfilepart.The
MPPART_INFOchanges are useless after this integration, so the above fix and this integration are combined into a single(this) PR.🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.