1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411
//! A safer abstraction for `ioctl`.
//!
//! The `ioctl` system call is very open-ended, supporting a variety of
//! different operations with different argument and result types, with the
//! valid operations varying drastically based on which underlying driver or
//! type of device the file represents. Passing the wrong kind of value to the
//! wrong request can cause memory corruption.
//!
//! To make `ioctl` a _little_ safer to use, this module provides the building
//! blocks for request constants that also include information about the
//! argument and result types, so that the [`super::File::ioctl`] method can
//! then provide a type-safe interface as long as these constants are defined
//! correctly. [`IoctlReq`] implementations can be defined in other crates that
//! provide support for particular device types or device drivers.
use core::mem::MaybeUninit;
use linux_unsafe::args::AsRawV;
use linux_unsafe::{int, ulong};
/// Represents a device type that can have `ioctl` requests implemented for it.
///
/// Implementations of this type should typically be zero-sized types, because
/// they are used only as markers for annotating `File` objects using
/// [`super::File::to_device`].
///
/// This is just a marker trait used to check type safety for
/// [`super::File::ioctl`]; it has no behavior of its own and merely permits
/// the safe abstraction to block trying to use ioctl requests intended for
/// another device type which might therefore cause memory corruption if the
/// argument type is incorrect.
pub trait IoDevice {}
/// Implemented by [`IoDevice`] implementations that are "sub-devices" of
/// another device, specified as type parameter `Parent`.
///
/// This is just a marker trait used to check type safety for
/// [`super::File::ioctl`]; it has no behavior of its own and merely permits
/// the safe abstraction to send requests that were intended for the parent
/// device type to files representing the implementer (the "child").
///
/// Devices don't actually need to form a strict tree. It is fine for a device
/// type to have multiple parents, or for the structure implied by this trait
/// to not resemble a tree at all, as long as the safety guarantees are met.
/// If A is parent of B and B is parent of C then A is not _automatically_
/// parent of C unless also explicitly implemented.
///
/// **Safety:** The implementer must be able to safely accept all of the
/// `ioctl` requests of `Parent` without compromising memory safety. The
/// parent requests do not necessarily need to _succeed_; it is sufficient
/// for them to fail safely without making any use of the given argument.
pub unsafe trait SubDevice<Parent: IoDevice>: IoDevice {}
/// Any `IoDevice` type can by definition safely accept its own `ioctl` requests,
/// assuming that those requests are themselves defined per the safety
/// requirements of [`IoctlReq`].
unsafe impl<T: IoDevice> SubDevice<T> for T {}
/// Represents a particular request that can be issue with the `ioctl` system call.
///
/// Safety: Implementers must ensure that they only generate valid combinations
/// of `ioctl` request and raw argument.
pub unsafe trait IoctlReq<'a, Device: IoDevice> {
/// The type that the caller will provide when using this `ioctl` command.
///
/// Use `()` for requests that don't need a caller-provided argument, such
/// as those which only return some data.
type ExtArg
where
Self: 'a;
/// The type of some temporary memory that the request needs to do its
/// work.
///
/// For a request that only returns data, this will typically
/// describe the layout of the returned data, which the kernel will
/// then populate. For requests that don't need this, use `()`.
type TempMem;
/// The type of argument that will be passed to the raw system call.
type RawArg: AsRawV;
/// The type of the result of the `fcntl` call.
type Result
where
Self: 'a;
/// Prepare the `cmd` and `arg` values for a `ioctl` system call.
///
/// The `arg` parameter is the argument provided by the caller of the
/// [`super::File::ioctl`] function. `temp_mem` is a reference to
/// uninitialized memory of appropriate size and alignment for
/// [`Self::TempMem`], which the implementer can either leave uninitialized
/// for the kernel to populate or pre-initialize with data the
/// kernel will expect to find there.
fn prepare_ioctl_args(
&self,
arg: &Self::ExtArg,
temp_mem: &mut MaybeUninit<Self::TempMem>,
) -> (ulong, Self::RawArg);
/// Prepare a raw successful result from a `ioctl` call to be returned.
fn prepare_ioctl_result(
&self,
raw: int,
arg: &Self::ExtArg,
temp_mem: &MaybeUninit<Self::TempMem>,
) -> Self::Result;
}
/// Constructs a new read-only [`IoctlReq`] with a fixed request code that
/// passes no payload to `ioctl` and returns its result in the system call
/// return value.
///
/// Safety: Callers must ensure that the given `request` is valid.
pub const unsafe fn ioctl_no_arg<Device, Result>(request: ulong) -> IoctlReqNoArgs<Device, Result>
where
*mut Result: AsRawV,
Device: IoDevice,
Result: FromIoctlResult<int>,
{
IoctlReqNoArgs::<Device, Result> {
request,
_phantom: core::marker::PhantomData,
}
}
/// Constructs a new read-only [`IoctlReq`] with a fixed request code and
/// a result type that maps directly to the data the kernel will
/// provide.
///
/// Safety: Callers must ensure that the given `request` is valid, that
/// type `T` describes what this request expects to get a pointer to, and
/// that the kernel will populate the given `T` object with data that is
/// consistent with Rust's expectations for the given type.
pub const unsafe fn ioctl_read<Device, Result>(request: ulong) -> IoctlReqRead<Device, Result>
where
*mut Result: AsRawV,
Device: IoDevice,
Result: Copy,
{
IoctlReqRead::<Device, Result> {
request,
_phantom: core::marker::PhantomData,
}
}
/// Constructs a new write-only [`IoctlReq`] with a fixed request code and
/// an argument type that the data the kernel expects to recieve directly as
/// its argument, without any pointer indirection.
///
/// Safety: Callers must ensure that the given `request` is valid, that
/// type `T` describes what this request expects to get as its argument.
pub const unsafe fn ioctl_write_val<Device, Arg, Result>(
request: ulong,
) -> IoctlReqWriteVal<Device, Arg, Result>
where
Arg: AsRawV,
Device: IoDevice,
Result: FromIoctlResult<int>,
{
IoctlReqWriteVal::<Device, Arg, Result> {
request,
_phantom: core::marker::PhantomData,
}
}
/// Constructs a new write-only [`IoctlReq`] with a fixed request code and
/// an argument type that maps directly to the data the kernel expects
/// to receive a pointer to.
///
/// Safety: Callers must ensure that the given `request` is valid, that
/// type `T` describes what this request expects to get a pointer to, and
/// that it isn't possible for any value of that type to cause the kernel
/// to violate memory safety. In particular, the kernel must not modify
/// the given memory, because the safe caller will provide a shared reference.
pub const unsafe fn ioctl_write<Device, Arg, Result>(
request: ulong,
) -> IoctlReqWrite<Device, Arg, Result>
where
*const Arg: AsRawV,
Device: IoDevice,
Result: FromIoctlResult<int>,
{
IoctlReqWrite::<Device, Arg, Result> {
request,
_phantom: core::marker::PhantomData,
}
}
/// Implementation of [`IoctlReq`] with a fixed `cmd` and passing no arguments
/// at all, just returning the kernel's result value.
///
/// This is for the less common `ioctl` requests that indicate more than just
/// success in their result, and so callers need to obtain that result.
#[repr(transparent)]
pub struct IoctlReqNoArgs<Device: IoDevice, Result> {
request: ulong,
_phantom: core::marker::PhantomData<(Device, Result)>,
}
unsafe impl<'a, Device, Result> IoctlReq<'a, Device> for IoctlReqNoArgs<Device, Result>
where
Result: 'a + FromIoctlResult<int>,
Device: 'a + IoDevice,
{
type ExtArg = ();
type TempMem = ();
type RawArg = ();
type Result = Result;
#[inline(always)]
fn prepare_ioctl_args(
&self,
_: &Self::ExtArg,
_: &mut MaybeUninit<Self::TempMem>,
) -> (ulong, Self::RawArg) {
(self.request, ())
}
#[inline(always)]
fn prepare_ioctl_result(
&self,
raw: int,
_: &Self::ExtArg,
_: &MaybeUninit<Self::TempMem>,
) -> Self::Result {
Self::Result::from_ioctl_result(&raw)
}
}
/// Implementation of [`IoctlReq`] with a fixed `cmd` value and passing a
/// pointer to a zeroed memory block of type `Result` directly through to the
/// underlying system call and then returnin a copy of that memory.
#[repr(transparent)]
pub struct IoctlReqRead<Device: IoDevice, Result>
where
*mut Result: AsRawV,
Result: Copy,
{
request: ulong,
_phantom: core::marker::PhantomData<(Device, Result)>,
}
unsafe impl<'a, Device, Result> IoctlReq<'a, Device> for IoctlReqRead<Device, Result>
where
*mut Result: AsRawV,
Result: 'a + Copy,
Device: 'a + IoDevice,
{
type ExtArg = ();
type TempMem = Result;
type RawArg = *mut Result;
type Result = Result;
#[inline(always)]
fn prepare_ioctl_args(
&self,
_: &Self::ExtArg,
temp_mem: &mut MaybeUninit<Self::TempMem>,
) -> (ulong, Self::RawArg) {
(self.request, temp_mem.as_mut_ptr())
}
#[inline(always)]
fn prepare_ioctl_result(
&self,
_: int,
_: &Self::ExtArg,
temp_mem: &MaybeUninit<Self::TempMem>,
) -> Self::Result {
unsafe { temp_mem.assume_init() }
}
}
/// Implementation of [`IoctlReq`] with a fixed `cmd` value and passing a
/// direct value from memory, without pointer indirection.
#[repr(transparent)]
pub struct IoctlReqWriteVal<Device: IoDevice, Arg, Result = int>
where
Arg: AsRawV,
{
request: ulong,
_phantom: core::marker::PhantomData<(Device, Arg, Result)>,
}
unsafe impl<'a, Device, Arg, Result> IoctlReq<'a, Device> for IoctlReqWriteVal<Device, Arg, Result>
where
Arg: 'a + AsRawV,
Result: 'a + FromIoctlResult<int>,
Device: 'a + IoDevice,
{
type ExtArg = Arg;
type TempMem = ();
type RawArg = Arg;
type Result = Result;
#[inline(always)]
fn prepare_ioctl_args(
&self,
arg: &Self::ExtArg,
_: &mut MaybeUninit<Self::TempMem>,
) -> (ulong, Arg) {
(self.request, *arg)
}
#[inline(always)]
fn prepare_ioctl_result(
&self,
ret: int,
_: &Self::ExtArg,
_: &MaybeUninit<Self::TempMem>,
) -> Self::Result {
Result::from_ioctl_result(&ret)
}
}
/// Implementation of [`IoctlReq`] with a fixed `cmd` value and passing a
/// pointer to an argument value in memory.
#[repr(transparent)]
pub struct IoctlReqWrite<Device: IoDevice, Arg, Result = int>
where
*const Arg: AsRawV,
{
request: ulong,
_phantom: core::marker::PhantomData<(Device, Arg, Result)>,
}
unsafe impl<'a, Device, Arg, Result> IoctlReq<'a, Device> for IoctlReqWrite<Device, Arg, Result>
where
*const Arg: AsRawV,
Arg: 'a,
Result: 'a + FromIoctlResult<int>,
Device: 'a + IoDevice,
{
type ExtArg = &'a Arg;
type TempMem = ();
type RawArg = *const Arg;
type Result = Result;
#[inline(always)]
fn prepare_ioctl_args(
&self,
arg: &Self::ExtArg,
_: &mut MaybeUninit<Self::TempMem>,
) -> (ulong, *const Arg) {
(self.request, (*arg) as *const Arg)
}
#[inline(always)]
fn prepare_ioctl_result(
&self,
ret: int,
_: &Self::ExtArg,
_: &MaybeUninit<Self::TempMem>,
) -> Self::Result {
Result::from_ioctl_result(&ret)
}
}
/// Trait for types that can be constructed automatically from `ioctl` results
/// from requests with a given argument type and temporary value type.
pub trait FromIoctlResult<Raw> {
fn from_ioctl_result(raw: &Raw) -> Self;
}
impl FromIoctlResult<int> for int {
fn from_ioctl_result(raw: &int) -> Self {
*raw
}
}
impl<Device: IoDevice> FromIoctlResult<int> for super::File<Device> {
fn from_ioctl_result(raw: &int) -> Self {
unsafe { super::File::from_raw_fd(*raw) }
}
}
#[allow(non_snake_case)]
const fn _IOC(dir: ulong, typ: ulong, nr: ulong, size: ulong) -> ulong {
(dir << 30) | (typ << 8) | (nr << 0) | (size << 16)
}
/// Equivalent to the kernel macro `_IO` for defining ioctl request numbers that
/// neither read nor write within the standard numbering scheme.
#[allow(non_snake_case)]
pub const fn _IO(typ: ulong, nr: ulong) -> ulong {
_IOC(0, typ, nr, 0)
}
/// Equivalent to the kernel macro `_IOR` for defining ioctl request numbers
/// where userspace reads data from the kernel.
#[allow(non_snake_case)]
pub const fn _IOR(typ: ulong, nr: ulong, size: ulong) -> ulong {
_IOC(2, typ, nr, size)
}
/// Equivalent to the kernel macro `_IOW` for defining ioctl request numbers
/// where userspace writes data to the kernel.
#[allow(non_snake_case)]
pub const fn _IOW(typ: ulong, nr: ulong, size: ulong) -> ulong {
_IOC(1, typ, nr, size)
}
/// Equivalent to the kernel macro `_IOWR` for defining ioctl request numbers
/// where userspace writes data to the kernel _and_ the kernel returns data
/// back to userspace.
#[allow(non_snake_case)]
pub const fn _IOWR(typ: ulong, nr: ulong, size: ulong) -> ulong {
_IOC(1 | 2, typ, nr, size)
}