One thing that bit me on a patch like this: reloading php-fpm is not the same as restarting it. A reload lets old workers finish their current requests, so a long lived upload can keep a vulnerable worker serving for minutes after you've called the box patched. For these I restart outright now, and accept the minute of dropped connections as the price.
Good point! We agree that a full restart is the safer choice for critical security patches. Making sure old workers are completely replaced is just as important as updating the PHP runtime itself. Better to accept a brief interruption than leave vulnerable processes running.
Kamran Khan
Full-Stack Web Developer (React.js + Laravel) | Dashboards, SaaS Apps & Management Systems for Global Clients
One thing that bit me on a patch like this: reloading php-fpm is not the same as restarting it. A reload lets old workers finish their current requests, so a long lived upload can keep a vulnerable worker serving for minutes after you've called the box patched. For these I restart outright now, and accept the minute of dropped connections as the price.