|
From: | Paolo Bonzini |
Subject: | Re: [PATCH v4 01/12] mm/shmem: Introduce F_SEAL_INACCESSIBLE |
Date: | Tue, 8 Mar 2022 13:17:02 +0100 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 |
On 3/7/22 14:26, Chao Peng wrote:
In pseudo-Rust, this is the difference between: fn convert_to_private(in: &mut Memfd) and fn convert_to_private(in: Memfd) -> PrivateMemoryFd This doesn't map particularly nicely to the kernel, though.I understand this Rust semantics and the difficulty to handle races. Probably we should not expose F_SEAL_INACCESSIBLE to userspace, instead we can use a new in-kernel flag to indicate the same thing. That flag should be set only when the memfd is created with MFD_INACCESSIBLE.
Yes, I like this. Paolo
[Prev in Thread] | Current Thread | [Next in Thread] |