Bug #76205 [Com]: PHP-FPM sporadic crash when running Infinitewp

Edit report at https://bugs.php.net/bug.php?id=76205&edit=1 ID: 76205 Comment by: spam2 at rhsoft dot net Reported by: post at minhost dot no Summary: PHP-FPM sporadic crash when running Infinitewp Status: Closed Type: Bug Package: opcache Operating System: CentOS 7.4 PHP Version: 7.1.16 Assigned To: dmitry Block user comment: N Private report: N New Comment: even if you ar enot worth an answer by your bloody ignorance, maybe others can learn - "Thanks. I just hope I am getting it correct. I am manually removing and copy/paste line by line from this patch" is insane - "patch1.patch" belo w is just the patch downloaded and apllied as every sane person does the few actions from the script below would have answered "Can you please confirm that I can use the patch http://git.php.net/?p=php-src.git;a=patch;h=5b3e1ded356dc877aa246d28e71e69286b8829b5 directly in PHP 7.1.17" and just started compile PHP [harry@srv-rhsoft:/downloads/build-php]$ ls insgesamt 12M -rw-r----- 1 harry verwaltung 2,9K 2018-05-03 23:38 patch1.patch -rwx------ 1 harry verwaltung 202 2018-05-03 23:40 build.sh -rw-r----- 1 harry verwaltung 12M 2018-05-03 23:17 php-7.1.17.tar.xz [harry@srv-rhsoft:/downloads/build-php]$ cat build.sh #!/bin/bash PHP_VERSION="7.1.17" rm -rf ./php-$PHP_VERSION tar xfJ ./php-$PHP_VERSION.tar.xz -C ./ cp patch1.patch ./php-$PHP_VERSION cd ./php-$PHP_VERSION patch -p1 --fuzz=0 < patch1.patch ./configure [harry@srv-rhsoft:/downloads/build-php]$ ./build.sh patching file ext/opcache/zend_file_cache.c Hunk #1 succeeded at 524 (offset -2 lines). Hunk #2 succeeded at 547 (offset -2 lines). Hunk #3 succeeded at 1144 (offset -2 lines). Hunk #4 succeeded at 1165 (offset -2 lines). checking for grep that handles long lines and -e... /usr/bin/grep checking for egrep... /usr/bin/grep -E checking for a sed that does not truncate output... /usr/bin/sed checking build system type... x86_64-unknown-linux-gnu checking host system type... x86_64-unknown-linux-gnu checking target system type... x86_64-unknown-linux-gnu Previous Comments: ------------------------------------------------------------------------ [2018-05-03 19:13:36] post at minhost dot no @spam2, Not one of my comment here is about how to apply the current patch. I have only asked if I can use the patch directly at PHP 7.1.17, and also asked about a committ that is not included in the patch. You are not contributing with your comments, and I will ignore any future comments from you. ------------------------------------------------------------------------ [2018-05-03 19:08:10] spam2 at rhsoft dot net the only one making noise here is you because you could have saved at least 4 comments by just deal with patches like the rest of the world smart people carry their patches in build scripts / rpm specs over years without touch the tarball ever - mine for httpd to not send any server header is untouched since httpd 2.4 was released why? because they are agnostic to other changes in different areas of the same file and if they needs to be rebased patch simply fails and you take notice ------------------------------------------------------------------------ [2018-05-03 18:40:29] post at minhost dot no @spam2, you are wrong. _I_ am applying this patch manually. And I have not asked what other people think about that. So please don't make noise in the comment field. ------------------------------------------------------------------------ [2018-05-03 18:22:56] spam2 at rhsoft dot net do yourself a favor and look at "man patcz" - nobody is applying patches line by line and by hand ------------------------------------------------------------------------ [2018-05-03 18:07:09] post at minhost dot no when I download the current snapshot I see that zend_file_cache.c line number 100 changed from ((char*)(ptr) < (char*)script->size) to ((char*)(ptr) <= (char*)script->size) should I add that change to? Or is it safe to use your commit without above change? ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=76205 -- Edit this bug report at https://bugs.php.net/bug.php?id=76205&edit=1