Jan Behrens

Link to the respective subsection: https://doc.rust-lang.org/reference/destructors.html#temporary-lifetime-extension

Related issues: * https://github.com/rust-lang/rust-bindgen/issues/1594 * https://github.com/rust-lang/rust-bindgen/issues/316

There exists an easy workaround when comparing (small) constants such as 1, 2, 3, or -1, -2 with a `c_int` (or any other C type returned by a function, which...

> @behlendorf how does `zfs allow` resolve this issue? I don't think resolves this issue. This issue (#3963) should be reopened, see also #9028.

Apparently `Sender`s without `Receiver`s show some (maybe) surprising behavior: ``` use tokio::sync::watch; #[allow(unused_variables)] fn main() { let (sender, receiver) = watch::channel("initial"); //drop(receiver); // try to uncomment sender.send("updated").ok(); let receiver2 =...

> This issue has been automatically marked as "stale" because it has not had any activity for a while. It will be closed in 90 days if no further activity...

Note that if https://github.com/openzfs/zfs/commit/acb33ee1c169bf1c1f687db18fa1815ffa68f246 lands, there may be more people exposed to this potentially security related issue.

> * We patch the code to set both nosuid and nosgid on automounts in .zfs by default, controllable by a kernel module parameter. Note that there are more security...

> […] (most of?) the other[s] [security implications] can only be prevented by not giving access in the first place […] This argument *(edit: without the "most of" restriction)* is...

> I think we are pretty much on the same page :) when I wrote "not giving access in the first place" I was referring to the snapshot, not the...