search for: into_foreign

...happens if implementers don't do this? > > If this is a safety requirement, we need to find a different way to > enforce it. > > > This is the worst part of this patch by far, unfortunately. If one doesn't do this, then s/he will leak the `data` field passed in through into_foreign() here: > + // SAFETY: `self.ptr` is valid as per the type invariant. > + let res = unsafe { > + bindings::virtqueue_add_sgs( > + self.ptr, > + sgs.as_mut_ptr(), > + num_out as u32, > + num_...

This used to be a single patch, but I split it into two with the addition of struct Scatterlist. Again a bit new with Rust submissions. I was told by Gary Guo to rebase on top of rust-next, but it seems *very* behind? The first patch does not build on its own due to a dead_code warning. It is hard to not have dead code when one is adding infrastructure to be used by others at a later