Message398956
ERROR_NETWORK_ACCESS_DENIED (65) should probably be added to the ignore list. I don't know whether it occurs in practice, but we have it mapped to EACCES in PC/errmap.h. The common access error is ERROR_ACCESS_DENIED (5), even on a UNC share with restricted access.
Add ERROR_DEV_NOT_EXIST (55) only if you have a case that fails with this error code. It's from the NT status code STATUS_DEVICE_DOES_NOT_EXIST. This might occur when trying to automount a device that's pending removal (see the implementation in ReactOS IopMountVolume [1]), but I can't create this condition. I think a device object would need to be practically stuck in the pending removal state for this to be a practical problem.
ERROR_LOCK_VIOLATION (33) isn't relevant. It's an I/O access error for a locked range of a file. realpath() doesn't read or write file data.
For the others, I'd wait for an issue to be reported.
---
[1] https://github.com/reactos/reactos/blob/master/ntoskrnl/io/iomgr/volume.c#L457 |
|
Date |
User |
Action |
Args |
2021-08-04 21:46:25 | eryksun | set | recipients:
+ eryksun, paul.moore, tim.golden, zach.ware, steve.dower, Spacetown |
2021-08-04 21:46:25 | eryksun | set | messageid: <1628113585.65.0.875049513717.issue44817@roundup.psfhosted.org> |
2021-08-04 21:46:25 | eryksun | link | issue44817 messages |
2021-08-04 21:46:25 | eryksun | create | |
|