opcache, file caching: Avoid problems with multiple pools/users
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 40.4k
- Forks
- 8.1k
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 96
Description
Description
It can happen that files in the file_cache collide. If they come from separate pools with separate users it can happen that one pool/user added a file and it can't be opened/overwritten by the other.
Can this be avoided by using the full file-path in the cache, maybe placeholders for the poolname or so? If those are separate pools then separate owners would not cause a collision.
PHP Version
PHP 8.5.7 (cli) (built: Jun 2 2026 20:59:56) (NTS gcc x86_64)
Copyright (c) The PHP Group
Built by Remi's RPM repository <https://rpms.remirepo.net/> #StandWithUkraine
Zend Engine v4.5.7, Copyright (c) Zend Technologies
with Zend OPcache v8.5.7, Copyright (c), by Zend Technologies
Operating System
RHEL 9
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing OPcache's file_cache handling and how cache paths are derived for separate pools and users. Confirm the collision and define completion as preventing one pool/user from blocking another when adding, opening, or overwriting cached files; no specific source file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, php
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100