touch: use write-open + futimens on Unix to trigger IN_CLOSE_WRITE #9813
+89
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…inux - Add `try_futimens_via_write_fd` function for Unix systems to open files write-only and set times using `futimens`, ensuring inotify watchers detect file closure after touch. - Modify `update_times` to attempt this method before falling back to `set_file_times`, improving compatibility with file monitoring tools on Linux. - Include necessary imports for Unix-specific operations.
- Updated the spell-checker comment to include 'futimens', likely a system call or function name, to avoid false positives in code spell-checking.
sylvestre
reviewed
Dec 24, 2025
src/uu/touch/src/touch.rs
Outdated
| }, | ||
| ]; | ||
|
|
||
| let rc = unsafe { libc::futimens(file.as_raw_fd(), times.as_ptr()) }; |
Contributor
There was a problem hiding this comment.
maybe use https://docs.rs/nix/latest/nix/sys/stat/fn.futimens.html to avoid the unsafe ?
sylvestre
reviewed
Dec 24, 2025
| } | ||
|
|
||
| #[cfg(unix)] | ||
| fn try_futimens_via_write_fd(path: &Path, atime: FileTime, mtime: FileTime) -> std::io::Result<()> { |
Contributor
There was a problem hiding this comment.
please document this function. and explain what is futimens
Contributor
|
is it possible to add tests ? thanks |
…time setting - Add nix and tempfile dependencies to Cargo.toml and Cargo.lock - Replace unsafe libc::futimens calls with nix::sys::stat::futimens for better safety and portability - Introduce try_futimens_via_write_fd function using nix abstractions - Add unit tests to verify futimens functionality on Unix systems This change reduces unsafe code usage and leverages a Rust-friendly library for Unix-specific operations.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Make
touchopen regular files for write and callfutimenson the fd (Unix only). This matches GNU touch behavior and ensures inotify emitsIN_CLOSE_WRITEwhen timestamps are updated.Motivation
Some inotify-based reloaders watch only
IN_CLOSE_WRITE. With the current path-based timestamp update,touchemits onlyIN_ATTRIB, so those watchers miss the change. This caused infinite loops in downstream tests (e.g., 0 A.D. hotload tests on Ubuntu Questing).Changes
OpenOptions::new().write(true)and callfutimenson the fd for regular files.set_file_timespath-based update when open/futimens fails or the target is not a regular file.Testing
cargo test -p uu_touchNotes
related
#9812