Closed
Bug 967711
Opened 11 years ago
Closed 10 years ago
HTTP cache v2: check usage of CacheFile::mHandle is always threadsafe
Categories
(Core :: Networking: Cache, defect)
Core
Networking: Cache
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: mayhemer, Unassigned)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
(deleted),
patch
|
Details | Diff | Splinter Review |
I've seen references in CacheFile to mHandle out of the file's lock. Maybe it's correct, maybe not. Worth checking on it.
Reporter | ||
Updated•11 years ago
|
OS: Windows 7 → All
Hardware: x86_64 → All
Reporter | ||
Comment 1•11 years ago
|
||
One of them is at CacheFile::OnFileOpened where mHandle is passed to CacheFileMetadata outside the file's lock.
Reporter | ||
Comment 2•11 years ago
|
||
..since it doesn't need it.
Reporter | ||
Comment 3•10 years ago
|
||
Not found any stack with CacheFile in signature that would seem to be suspected.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•