| Ticket UUID: | ce32712f83f0d30051adb6a53e11f9e338a9944 | ||
| Title: | Inconsistent locking during zipfs initialization | ||
| Type: | Bug | Created on: | 2025-10-03 10:04:51 |
| Submitter: | apnadkarni | Assigned to: | nobody |
| Subsystem: | - New Builtin Commands | Severity: | Minor |
| Priority: | 5 Medium | Last modified: | 2025-12-09 09:01:27 |
| Status: | Open | Closed by: | nobody |
| Resolution: | None | Closed on: | |
| Version: | 9.0.2 | ||
| Description: | ||||
|
Both the following sequences are seen in tclZipFs.c
and
I had added a TODO comment questioning this when fixing zipfs bugs during the 9.0 beta but forgot to revisit and just saw it today :-( | ||||
| User Comments: | ||||
dkf added on 2025-10-07 14:11:25:
Since it's a once-per-process setup, the flag is likely set to true before the process launches any more threads (that read the vfs). The different locks may be for the code that follows. If my thoughts are correct, moving the call to The memory barrier due to the function call is probably enough. jan.nijtmans added on 2025-12-09 09:01:27:
Ping? What's the status of this? | ||||
