Re: Re: [RFC] [Discussion] OPcache Static Cache
| From: | Jakub Zelenka | Date: | Mon, 01 Jun 2026 07:30:03 +0000 |
| Subject: | Re: Re: [RFC] [Discussion] OPcache Static Cache | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-131072@lists.php.net to get a copy of this message | ||
Hi,
On Mon, Jun 1, 2026 at 8:06 AM Go Kudo <zeriyoshi@gmail.com> wrote:
>
>
> 2026年5月17日(日) 0:19 Go Kudo <zeriyoshi@gmail.com>:
>
>> Hi internals,
>>
>> I'd like to start the discussion for a new RFC, OPcache Static Cache.
>>
>> RFC: https://wiki.php.net/rfc/opcache_static_cache
>> Implementation: https://github.com/php/php-src/pull/22052
>>
>
>
The FPM shared hosting part is a problem and I don't think this can be
default and probably cannot even be optional. The reason is that we
consider data leaks between pools as security issues so I don't think we
can have some feature that is actually causing a security issue. It will be
a bit tricky to decide what to do if this passes in the current form
because we would probably need to apply security fix and disable it. If you
really want to have it enabled, we would need to explicitly state in the
policy and docs that pool boundary is no longer considered as a security
boundary which would be quite problematic for some shared hosting that rely
on it. Maybe the solution would be to allow it only if there is one pool
enabled.
Kind regards,
Jakub