remove_dir_all_recursive: treat ELOOP the same as ENOTDIR#96234
remove_dir_all_recursive: treat ELOOP the same as ENOTDIR#96234bors merged 1 commit intorust-lang:masterfrom
Conversation
|
Hey! It looks like you've submitted a new PR for the library teams! If this PR contains changes to any Examples of
|
|
r? @thomcc (rust-highfive has picked a reviewer for you, use r? to override) |
|
According to https://man7.org/linux/man-pages/man2/open.2.html, @bors r+ |
|
📌 Commit cff3f1e has been approved by |
Rollup of 6 pull requests Successful merges: - rust-lang#93313 (Check if call return type is visibly uninhabited when building MIR) - rust-lang#96160 (Miri/interpreter debugging tweaks) - rust-lang#96167 (Replace sys/unix/weak AtomicUsize with AtomicPtr) - rust-lang#96168 (Improve AddrParseError description) - rust-lang#96206 (Use sys::unix::locks::futex* on wasm+atomics.) - rust-lang#96234 (remove_dir_all_recursive: treat ELOOP the same as ENOTDIR) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
On older Linux kernels (I tested on 4.4, corresponding to Ubuntu 16.04), opening a symlink using
O_DIRECTORY | O_NOFOLLOWreturnsELOOPinstead ofENOTDIR. We should handle it the same, since a symlink is still not a directory and needs to beunlinked.