Johnathan Van Why

> The current CI failure seems to be about MSRV. Can someone confirm? What are we doing about that? Our policy is to bump the MSRV whenever doing so is...

Oh, and I suggest increasing the toolchain versions in a separate PR, just in case the toolchain bump causes compilation failures for somebody else' PR. If the toolchain version increase...

# Idea: `Pin`-based Allow I think there's a sound design based on `Pin`'s `Drop` guarantee. The buffer to be shared must be part of a `!Unpin` type, which un-shares the...

> I have one soundness concern: shouldn't it be keeping track of whether it's currently `allow`ed with the kernel, so `Drop` doesn't double-unallow if you called `get_mut_buffer`? Double-unallow isn't a...

> There seems to be a problem due to one of the denos that uses `slint`. @jrvanwhy should we update the rust version to 1.82 or somehow disable that demo?...

Retrieving the current time (clock ticks, to be precise) is done by using the [alarm syscall driver](https://github.com/tock/tock/blob/master/doc/syscalls/00000_alarm.md). We do have a [library](https://github.com/tock/libtock-rs/blob/master/apis/alarm/src/lib.rs) for interfacing with the alarm syscall driver, but...

> platforms that really care would also use credentialed applications and verify them. I think you're asserting that all Tock deployments that care about preventing impersonation would have a form...

> I do agree that it could be retrofit, though. I think you could allow processes to self-service their security by providing one or both of the following commands: >...

Let me try to step back and give a high-level view of what we're trying to achieve with IPC authentication, and the available options for doing so. # Why does...

`boards/build_scripts/tock_kernel_layout.ld` is not x86-specific. At least on ARM and RISC-V, it is important for the stack to be at the bottom of the accessible RAM region, as per this comment:...