Skip to content

Fix the description of TimeoutFlags::ETIME_SUCCESS (#342) #345

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jul 18, 2025
Merged

Fix the description of TimeoutFlags::ETIME_SUCCESS (#342) #345

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions src/types.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -85,9 +85,9 @@ bitflags! {
/// unless one of the following flags is set (they may not both be set):
/// [`types::TimeoutFlags::BOOTTIME`] or [`types::TimeoutFlags::REALTIME`].
///
/// The default behavior when the timeout expires is to return a CQE with -libc::ETIME in
/// the res field. To change this behavior to have zero returned, include
/// [`types::TimeoutFlags::ETIME_SUCCESS`].
/// The default behavior when the timeout expires is to sever dependent links, as a failed
/// request normally would. To keep the links untouched include [`types::TimeoutFlags::ETIME_SUCCESS`].
/// CQE will still contain -libc::ETIME in the res field
#[derive(Debug, Clone, Copy, PartialEq, Eq, PartialOrd, Ord)]
pub struct TimeoutFlags: u32 {
const ABS = sys::IORING_TIMEOUT_ABS;
Expand Down
Loading