enricobuehler
dfebb9dfbb
undocumented_unsafe_blocks joins unsafe_op_in_unsafe_fn in
[workspace.lints], and the ~100 scattered per-file #![deny(...)] attributes
(85 files) are deleted — a new crate, or a new module in an old one, is now
covered on creation rather than on remembering. The per-file form is how
pf-vkhdr-layer, wdk-probe and half of pf-clipboard stayed uncovered.
There are THREE workspaces, so the claim is made three times: the main
Cargo.toml, packaging/windows/drivers (workspace table + [lints]
workspace = true in all seven members), and packaging/windows/pf-vkhdr-layer
(its [lints] table, previous commit). pf-update now opts into workspace
lints; the two vendored member snapshots (cros-codecs, usbip-sim) stay out
deliberately and now both say so.
Newly-covered fallout was two link-sanity tests (pyrowave-sys, libvpl-sys)
— proofs written. Stale prose that claimed the workspace held
unsafe_op_in_unsafe_fn at "warn" (it has been deny) or pointed at the
deleted attributes is corrected.
nvenc_core.rs is carved OUT of the unsafe_op_in_unsafe_fn fence: its
exemption rationale ("raw entry-table calls almost line for line") was
false — the file makes zero FFI calls. Its unsafe surface is C-union writes
whose soundness hangs on which codec arm is active, and its own 4:4:4 note
records the shipped bug (hevcConfig bytes stamped onto an AV1 config) that
per-operation blocks make visible. It now runs the strictest discipline in
the crate: clippy::multiple_unsafe_ops_per_block at deny, one union access
per block, each naming its codec guard.
Verified here: cargo fmt clean in all three workspaces; native clippy
-D warnings clean for everything that compiles on macOS (the three
pre-existing mac-native failures — pf-client-core wol.rs, pf-encode
dead-code/closure-call, probe mic_burst — reproduce on the clean tree).
Linux/Windows legs ride the .25/.133 gate.
23 lines
1.2 KiB
Rust
23 lines
1.2 KiB
Rust
//! Linux GPU zero-copy plumbing (plan §9), extracted from the host's `linux/zerocopy/` module
|
|
//! tree (plan §W6): the shared CUDA context + device buffers, the EGL/Vulkan dmabuf importers,
|
|
//! the isolated import-worker subprocess (client/proto/worker), the zero-copy policy latches, and
|
|
//! the dmabuf implicit-fence wait. Everything is Linux-only; on other targets this crate compiles
|
|
//! to an empty lib so dependents can carry a plain (non-target-gated) dependency.
|
|
//!
|
|
//! The `PixelFormat → DRM FourCC` mapping (`drm_fourcc`) deliberately does NOT live here — it
|
|
//! consumes the shared frame vocabulary, which sits ABOVE this crate (this crate provides the
|
|
//! `DeviceBuffer` that vocabulary's `FramePayload::Cuda` owns).
|
|
|
|
// Unsafe-proof program: every `unsafe {}` / `unsafe impl` carries a `// SAFETY:` proof, and
|
|
// `unsafe fn` bodies need explicit blocks (~45 functions' worth of raw driver calls used to sit
|
|
// outside that invariant). Both lints are enforced by the workspace `[workspace.lints]` tables.
|
|
|
|
/// Wait for a dmabuf's implicit read-ready fence (`DMA_BUF_IOCTL_EXPORT_SYNC_FILE` + poll).
|
|
#[cfg(target_os = "linux")]
|
|
pub mod dmabuf_fence;
|
|
|
|
#[cfg(target_os = "linux")]
|
|
mod imp;
|
|
#[cfg(target_os = "linux")]
|
|
pub use imp::*;
|