about summary refs log tree commit diff
path: root/compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
diff options
context:
space:
mode:
authorMatthias Krüger <matthias.krueger@famsik.de>2024-12-22 21:59:24 +0100
committerGitHub <noreply@github.com>2024-12-22 21:59:24 +0100
commitbd160f11f00823c5a3a9ee615907e238e44f2e81 (patch)
tree0efb6f1fafb734ced95ee897deb88da14206fa6b /compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp
parent303e8bd768526a5812bb1776e798e829ddb7d3ca (diff)
parentedfdfbe832db3495b242a31c405cdb0d77bd45d3 (diff)
downloadrust-bd160f11f00823c5a3a9ee615907e238e44f2e81.tar.gz
rust-bd160f11f00823c5a3a9ee615907e238e44f2e81.zip
Rollup merge of #130289 - intgr-forks:Permissions-readonly-vs-unix-root, r=ChrisDenton
docs: Permissions.readonly() also ignores root user special permissions

The root user can write to files without any (write) permission bits set. But this is not taken into account by `std::fs::Permissions.readonly()`.

The rustdoc for `readonly()` also mentions shortcomings later:

> On Unix-based platforms this checks if any of the owner, group or others write permission bits are set. It does not check if the current user is in the file’s assigned group. It also does not check ACLs.

But since this part already clarifies how it works -- it checks write permission bits -- I think it's not necessary to repeat the root user shortcomings here.
Diffstat (limited to 'compiler/rustc_llvm/llvm-wrapper/RustWrapper.cpp')
0 files changed, 0 insertions, 0 deletions