Opened 11 years ago
Last modified 6 months ago
#21602 new Cleanup/optimization
FileSystemStorage._save() Should Save to a Temporary Filename and Rename to Attempt to be Atomic
Reported by: | Kevin Stone | Owned by: | nobody |
---|---|---|---|
Component: | File uploads/storage | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | bcail | Triage Stage: | Accepted |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
When using FileSystemStorage based backend with say, staticfiles, creates a race condition where it's writing the intended destination file which can lead to race conditions where your web server can serve incomplete assets while they're being written.
Another case happens with post-processing since CachedStaticFilesStorage actually deletes the hash-named file before saving over it.
These issue should be circumventing by directing the writing to a temporary file name and then atomically renaming it to the intended destination. Even better, FileSystemStorage._save() has to site in a While-loop because of race conditions in get_available_name(). Instead, it could defer calling get_available_name until it's prepared to rename the file to its destination.
I'm working on implementing these changes in my own sub-class of FileSystemStorage (and CachedStaticFilesStorage to avoid the delete() call) and would be apply to submit them as a patch if there's interest.
Change History (4)
comment:1 by , 11 years ago
Triage Stage: | Unreviewed → Accepted |
---|
comment:2 by , 11 years ago
Type: | Uncategorized → Cleanup/optimization |
---|
comment:4 by , 6 months ago
Cc: | added |
---|
This should be easier to implement once the OS_OPEN_FLAGS are removed (they're currently deprecated).
Agreed that atomic rename should be used.