summaryrefslogtreecommitdiffstats
path: root/vendor/rustix/src/mm/msync.rs
diff options
context:
space:
mode:
Diffstat (limited to 'vendor/rustix/src/mm/msync.rs')
-rw-r--r--vendor/rustix/src/mm/msync.rs32
1 files changed, 32 insertions, 0 deletions
diff --git a/vendor/rustix/src/mm/msync.rs b/vendor/rustix/src/mm/msync.rs
new file mode 100644
index 000000000..7117a5067
--- /dev/null
+++ b/vendor/rustix/src/mm/msync.rs
@@ -0,0 +1,32 @@
+//! The `msync` function.
+//!
+//! # Safety
+//!
+//! `msync` operates on a raw pointer. Some forms of `msync` may mutate the
+//! memory or have other side effects.
+#![allow(unsafe_code)]
+
+use crate::{imp, io};
+use core::ffi::c_void;
+
+pub use imp::mm::types::MsyncFlags;
+
+/// `msync(addr, len, flags)`—Synchronizes a memory-mapping with its backing
+/// storage.
+///
+/// # Safety
+///
+/// `addr` must be a valid pointer to memory that is appropriate to
+/// call `msync` on. Some forms of `msync` may mutate the memory
+/// or evoke a variety of side-effects on the mapping and/or the file.
+///
+/// # References
+/// - [POSIX]
+/// - [Linux `msync`]
+///
+/// [POSIX]: https://pubs.opengroup.org/onlinepubs/9699919799/functions/msync.html
+/// [Linux `msync`]: https://man7.org/linux/man-pages/man2/msync.2.html
+#[inline]
+pub unsafe fn msync(addr: *mut c_void, len: usize, flags: MsyncFlags) -> io::Result<()> {
+ imp::mm::syscalls::msync(addr, len, flags)
+}