fs.mkdir/mkdirSync hang with {recursive: true} if name is invalid

[jeffrson]

• Version: 10.16.0, 11.14.0, 12.6.0
• Platform: Windows 10
• Subsystem: fs

If the name of the dir to be created is invalid, fs.mkdir never calls back and fs.mkdirSync blocks:

const fs = require('fs')

console.log("1")
fs.mkdir('invalid1:', {recursive: true}, (err) => {
  console.log("is not called")
  if (err) throw err
})

console.log("2")
fs.mkdirSync('invalid2:', {recursive: true})
console.log("is not reached")

BTW, the error message that is reported with {recursive: false} appears a bit strange:

Error: ENOENT: no such file or directory, mkdir 'invalid2:'

Wouldn't it be more convenient to use EPERM, EACCES or ENOTDIR?

[Hakerh400]

Colons on NTFS files systems on Windows denote file streams (source).

[jeffrson]

The error is the same for "invalid>", "invalid<" oder "invalid|".

[silverwind]

Those are all invalid characters on NTFS, see here.

Not sure if Node.js should do validation for those (and take a performance hit on every platform). There are modules like this which you can use to validate yourself.

The hang itself should probably be investigated, thought.

[jeffrson]

Yes - I know this module. However, it is not cross plattform as far as I can tell - ':', '<', '>','|' may be valid on Linux (although not necessarily recommended, I guess). Yes, of course I could distinguish platforms. But I could as well rely on "fs.mkdir" to fail, if something is wrong.

The point is, Node should, if it fails to create the directory for whatever reason, give a reasonable error and, of course, not hang - with { recursive: true } or not.

[bzoz]

This is similar to #27198, which was fixed by #27207.

For invalid filenames, uv_fs_mkdir returns UV_ENOENT, which confuses the fs.mkdir function. It constantly creates the parent directory then tries to create the invalid folder.

Made a libuv PR that makes it return UV_EINVAL for invalid filenames. This fixes this issue.