[issue33016] nt._getfinalpathname may use uninitialized memory
Alexey Izbyshev
report at bugs.python.org
Thu Mar 8 18:25:47 EST 2018
Alexey Izbyshev <izbyshev at ispras.ru> added the comment:
> We know that the path is valid because we have a handle (in this case the file system ensures that no parent directory in the path can be unlinked or renamed).
Thank you for pointing this out. I erroneously stated that the length of the path could increase between GetFinalPathNameByHandle calls because an intermediate directory could be renamed, but actually I've only checked that the last part can be renamed (or even deleted, though it'll still linger in inaccessible state until the handle is closed).
----------
_______________________________________
Python tracker <report at bugs.python.org>
<https://bugs.python.org/issue33016>
_______________________________________
More information about the Python-bugs-list
mailing list