Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:126164
Precedence: bulk
MIME-Version: 1.0
References: <27531d9d-9bfe-4acc-b9ab-80b1017e3038@app.fastmail.com>
 <CAEKnhAFU32EXh483QzR0LLUt+Jou4ejKjOXqBQ_G43wR7LW5cA@mail.gmail.com>
 <e8736456-218d-4a55-a595-e1346e1c6d20@app.fastmail.com> <CAEKnhAEAXCmnqfCEyqJbJWr-=XRDY31m2eJDA3WmX9HcA8a0kg@mail.gmail.com>
In-Reply-To: <CAEKnhAEAXCmnqfCEyqJbJWr-=XRDY31m2eJDA3WmX9HcA8a0kg@mail.gmail.com>
Date: Sun, 22 Dec 2024 09:42:19 +0000
Message-ID: <CAEKnhAF3=MzxtaHKtEchhPfm03=Ae_EqgZHQ3LUY=qdcH_+JJg@mail.gmail.com>
Subject: Re: [PHP-DEV] Discussion: Remove file statcache?
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000d772130629d8b22a"
From: bukka@php.net (Jakub Zelenka)

--000000000000d772130629d8b22a
Content-Type: text/plain; charset="UTF-8"

> I suppose a possible alternative would be to modify all file system
>> mutation functions (file_put_contents(), touch(), etc.) to flush the cache,
>> which for whatever reason doesn't happen now.  That would be above my skill
>> level, though, so someone else would need to do it.  Also, I don't know if
>> there's a good reason those functions don't clear the cache currently or if
>> it was just an oversight.
>>
>>
> As I said we could probably handle some stream cases more aggressively but
> it won't resolve the problem completely. We still have things like
> system("touch /file/path") which we cannot flush the stat cache for. And
> it's not just shell access - there might be some 3rd party extensions that
> operate on files or there might be other programs accessing files at the
> same time. So there are many places which we just cannot control.
>
>
Thinking about it, there might be a possibility to address it (at least on
Linux) using fanotify. Not sure about other platforms but maybe there are
some solutions to address it. Also it might get a bit complex and not sure
how much the solution is viable.

I guess we should first research and maybe PoC to which extend this can be
actually fixed. I will try to prioritize it and look into it in the coming
weeks.

Regards

Jakub

--000000000000d772130629d8b22a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><div class=3D"gmail_quote gmail=
_quote_container"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">
I suppose a possible alternative would be to modify all file system mutatio=
n functions (file_put_contents(), touch(), etc.) to flush the cache, which =
for whatever reason doesn&#39;t happen now.=C2=A0 That would be above my sk=
ill level, though, so someone else would need to do it.=C2=A0 Also, I don&#=
39;t know if there&#39;s a good reason those functions don&#39;t clear the =
cache currently or if it was just an oversight.<br><br></blockquote><div><b=
r></div><div>As I said we could probably handle some stream cases more aggr=
essively but it won&#39;t resolve the problem completely. We still have thi=
ngs like system(&quot;touch /file/path&quot;) which we cannot flush the sta=
t cache for. And it&#39;s not just shell access - there might be some 3rd p=
arty extensions that operate on files or there might be other programs acce=
ssing files at the same time. So there are many places which we just cannot=
 control.</div><div><br></div></div></div></blockquote><div>=C2=A0</div><di=
v>Thinking about it, there might be a possibility to address it (at least o=
n Linux) using fanotify. Not sure about other platforms but maybe there are=
 some solutions to address it. Also it might get a bit complex and not sure=
 how much the solution is viable.</div><div><br></div><div>I guess we shoul=
d first research and maybe PoC to which extend this can be actually fixed. =
I will try to prioritize it and look into it in the coming weeks.</div><div=
><br></div><div>Regards</div><div><br></div><div>Jakub</div></div></div>

--000000000000d772130629d8b22a--