Lines Matching full:safety

62 // SAFETY: It is allowed to call `misc_deregister` on a different thread from where you called
65 // SAFETY: All `&self` methods on this type are written to ensure that it is safe to call them in
74                 // SAFETY: The initializer can write to the provided `slot`.
77                 // SAFETY: We just wrote the misc device options to the slot. The miscdevice will
95         // SAFETY: This can only be called after a successful register(), which always
107         // SAFETY: We know that the device is registered by the type invariants.
199     /// # Safety
204         // SAFETY: The pointers are valid and for a file being opened.
210         // SAFETY: The open call of a file can access the private data.
213         // SAFETY: This is a miscdevice, so `misc_open()` set the private data to a pointer to the
219         // SAFETY:
234         // SAFETY: The open call of a file can access the private data.
240     /// # Safety
245         // SAFETY: The release call of a file owns the private data.
247         // SAFETY: The release call of a file owns the private data.
250         // SAFETY:
258     /// # Safety
266         // SAFETY: The caller provides a valid `struct kiocb` associated with a
269         // SAFETY: This is a valid `struct iov_iter` for writing.
278     /// # Safety
286         // SAFETY: The caller provides a valid `struct kiocb` associated with a
289         // SAFETY: This is a valid `struct iov_iter` for reading.
298     /// # Safety
306         // SAFETY: The mmap call of a file can access the private data.
308         // SAFETY: This is a Rust Miscdevice, so we call `into_foreign` in `open` and
312         // SAFETY: The caller provides a vma that is undergoing initial VMA setup.
314         // SAFETY:
325     /// # Safety
329         // SAFETY: The ioctl call of a file can access the private data.
331         // SAFETY: Ioctl calls can borrow the private data of the file.
334         // SAFETY:
345     /// # Safety
354         // SAFETY: The compat ioctl call of a file can access the private data.
356         // SAFETY: Ioctl calls can borrow the private data of the file.
359         // SAFETY:
370     /// # Safety
375         // SAFETY: The release call of a file owns the private data.
377         // SAFETY: Ioctl calls can borrow the private data of the file.
379         // SAFETY:
383         // SAFETY: The caller ensures that the pointer is valid and exclusive for the duration in