GruzzberryandClaude Opus 5.5 4e5db13927 fix(libkernel): follow a Windows symbolic link in chmod ...

_wchmod changes the read-only attribute of the path it is given, so on
Windows chmod through a symbolic link changed the link and left the file
it names unchanged, and a dangling link succeeded. A reparse point is now
opened through its target and the target's path is changed, as FreeBSD
11.4's sys_chmod passes FOLLOW: a missing target fails with ENOENT and a
link loop with ELOOP. The path lookup of a handle moves out of
WindowsDescriptorPath_nid_no_patch so both use it.

Co-Authored-By: Claude Opus 5.5 <[email protected]>

2026-10-23 14:40:15 +01:00

..

include

Merge pull request #8687 from cadenasynyster/fix/win-loop-errors

2026-10-23 21:08:52 +13:00

src

fix(libkernel): follow a Windows symbolic link in chmod

2026-10-23 14:40:15 +01:00