You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A-ioArea: `std::io`, `std::fs`, `std::net` and `std::path`C-bugCategory: This is a bug.O-linuxOperating system: LinuxT-libsRelevant to the library team, which will review and decide on the PR/issue.
It would be best to always use openat, otherwise there could be a race where the target directory is swapped with a symlink to some other directory and it then tries to delete descendants of the swapped one.
Enselic
added
C-bug
Category: This is a bug.
T-libs
Relevant to the library team, which will review and decide on the PR/issue.
A-io
Area: `std::io`, `std::fs`, `std::net` and `std::path`
and removed
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
labels
Sep 28, 2023
A-ioArea: `std::io`, `std::fs`, `std::net` and `std::path`C-bugCategory: This is a bug.O-linuxOperating system: LinuxT-libsRelevant to the library team, which will review and decide on the PR/issue.
On Linux
unlink()
might fail withENAMETOOLONG
butstd::fs::remove_dir_all
doesn't handle that and ignores the error, leaving the directory as it was.When the path is too long a parent directory should be
open()
ed instead andunlinkat()
should be called with the relative path.The text was updated successfully, but these errors were encountered: