Clippy lint · Correctness · checked with Clippy 0.1.99

clippy::non_octal_unix_permissions: Checks for non-octal values used to set Unix file permissions

What it meansChecks for non-octal values used to set Unix file permissions. It is in the correctness group and denied by default (the build fails).

Does it matter?

They will be converted into octal, creating potentially unintended file permissions.

Code that is almost certainly wrong. Denied by default: the build fails until you fix it or allow it.

How to fix it

Clippy can fix this one for you: run cargo clippy --fix (add --allow-dirty if you have uncommitted changes). Review the diff before you commit.

Flagged

use std::fs::OpenOptions;
use std::os::unix::fs::OpenOptionsExt;

let mut options = OpenOptions::new();
options.mode(644);

Write this instead

use std::fs::OpenOptions;
use std::os::unix::fs::OpenOptionsExt;

let mut options = OpenOptions::new();
options.mode(0o644);

Turn it off, or on

Allow it where it does not fit your code, as narrowly as you can:

On one item

#[allow(clippy::non_octal_unix_permissions)]
fn my_function() { /* ... */ }

Whole crate (Cargo.toml)

[lints.clippy]
non_octal_unix_permissions = "allow"

One run

cargo clippy -- -A clippy::non-octal-unix-permissions

The [lints] table needs Rust 1.74 or newer. In a workspace, put it under [workspace.lints.clippy] and add [lints] workspace = true to each member.

Correctnessgroup

denydefault level

yesfixed by cargo clippy --fix

1.53.0added in Rust

Clippy's own documentation

What it does

Checks for non-octal values used to set Unix file permissions.

Why is this bad?

They will be converted into octal, creating potentially unintended file permissions.

Example

use std::fs::OpenOptions;
use std::os::unix::fs::OpenOptionsExt;

let mut options = OpenOptions::new();
options.mode(644);

Use instead:

use std::fs::OpenOptions;
use std::os::unix::fs::OpenOptionsExt;

let mut options = OpenOptions::new();
options.mode(0o644);

From the Clippy lint list (0.1.99), part of the Rust project, MIT or Apache-2.0. Official entry.

Up next

Also worth your time

Did this answer your question?