chmod: behavioral divergence from coreutils when the target file is not accessible · uutils/coreutils#9789

(1 留言) (0 反應) (0 負責人)Rust (23,246 star) (1,852 fork)batch import

U - chmodgood first issue

描述

Component

chmod

Description

In Chmoder::chmod()

if !file.exists() {
    // .........
}

Path::exists() is used to determine whether a file is existed. Because Path::exists() will return false when there is a metadata access errors, including PermissionDenied, it can misclassify existing but inaccessible paths as non-existent, producing incorrect result.

Test / Reproduction Steps

core_sbx$ sudo mkdir locked
core_sbx$ sudo touch locked/file
core_sbx$ sudo chmod 000 locked
core_sbx$ ../../coreutils/target/release/chmod 000 locked/file
../../coreutils/target/release/chmod: cannot access 'locked/file': No such file or directory
core_sbx$ chmod 000 locked/file
chmod: cannot access 'locked/file': Permission denied

Impact

Behavioral divergence from GNU coreutils: scripts and tooling may treat No such file differently from Permission denied.

貢獻者指南

技術棧: rust
領域: cli
議題類型: bug
難度: 2
預計時間: under 1 hour
活動狀態: fresh
清晰度: clear
前置要求: RustFile permissionsPath::exists() behavior
新手友善度: 85
研究方向: Examine the `chmod` implementation in the repository, particularly the `Chmoder::chmod()` method. Replace the `Path::exists()` call with `File::open()` or `metadata()` to properly handle permission errors. Ensure the error message matches GNU coreutils when the file exists but is inaccessible. Update any relevant tests to cover this case.