Bug #78296 [Ana->Csd]: is_file fails to detect file

Edit report at https://bugs.php.net/bug.php?id=78296&edit=1 ID: 78296 Updated by: cmb@php.net Reported by: v-altruo at microsoft dot com Summary: is_file fails to detect file -Status: Analyzed +Status: Closed Type: Bug Package: Scripting Engine problem Operating System: Windows PHP Version: 7.2Git-2019-07-16 (Git) Assigned To: cmb Block user comment: N Private report: N New Comment: Automatic comment on behalf of cmbecker69@gmx.de Revision: http://git.php.net/?p=php-src.git;a=commit;h=bb735c9e9e4a2ca2686a141ffe867f60ee0053c3 Log: Fix #78296: is_file fails to detect file Previous Comments: ------------------------------------------------------------------------ [2019-11-25 11:29:00] cmb@php.net The following pull request has been associated: Patch Name: Fix #78296: is_file fails to detect file On GitHub: https://github.com/php/php-src/pull/4943 Patch: https://github.com/php/php-src/pull/4943.patch ------------------------------------------------------------------------ [2019-11-25 11:07:29] cmb@php.net My assessment so far was not quite right. Actually, the problem is that[1]: | File I/O functions in the Windows API convert "/" to "\" as part | of converting the name to an NT-style name, except when using the | "\\?\" prefix as detailed in the following sections. This is already correctly handled on systems supporting PathCchCanonicalizeEx(), which have the registry setting LongPathsEnabled disabled, but not for other systems. Also, mkdir() is affected by this issue if the path is between 248 and 259 characters long. [1] <https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file> ------------------------------------------------------------------------ [2019-07-16 13:05:05] cmb@php.net The following pull request has been associated: Patch Name: Fix #78296: is_file fails to detect file On GitHub: https://github.com/php/php-src/pull/4421 Patch: https://github.com/php/php-src/pull/4421.patch ------------------------------------------------------------------------ [2019-07-16 12:26:08] cmb@php.net > It seems that the file and directory management functions (such > as CreateFileW()) don't accept long paths prefixed by \\?\. Wrong conclusion. Actually we're not properly normalizing the path, if the canonicalized path has the same length as before. ------------------------------------------------------------------------ [2019-07-16 10:52:48] cmb@php.net Thanks for reporting! This is a rather interesting issue. At first I have not been able to reproduce the test failure. Then I checked the registry key LongPathsEnabled[1] and found that it was disabled. After enabling it, the test failed for me as well. It seems that the file and directory management functions (such as CreateFileW()) don't accept long paths prefixed by \\?\. The following patch makes the test pass for LongPathsEnabled set to true: win32/ioutil.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/win32/ioutil.h b/win32/ioutil.h index 34104a3f45..7937718766 100644 --- a/win32/ioutil.h +++ b/win32/ioutil.h @@ -190,7 +190,7 @@ __forceinline static wchar_t *php_win32_ioutil_conv_any_to_w(const char* in, siz } /* Only prefix with long if it's needed. */ - if (mb_len >= _MAX_PATH) { + if (0) { size_t new_mb_len; ret = (wchar_t *) malloc((mb_len + PHP_WIN32_IOUTIL_LONG_PATH_PREFIX_LENW + 1) * sizeof(wchar_t)); [1] <https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file#enable-long-paths-in-windows-10-version-1607-and-later> ------------------------------------------------------------------------ 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=78296 -- Edit this bug report at https://bugs.php.net/bug.php?id=78296&edit=1