Re: [PATCH v11 2/8] mm: rust: add vm_area_struct methods that require read access

[Andreas Hindborg <a.hindborg@kernel.org>]

"Alice Ryhl" <aliceryhl@google.com> writes:

> On Mon, Dec 16, 2024 at 3:51 PM Andreas Hindborg <a.hindborg@kernel.org> wrote:
>>
>>
>> > +
>> > +    /// Zap pages in the given page range.
>> > +    ///
>> > +    /// This clears page table mappings for the range at the leaf level, leaving all other page
>> > +    /// tables intact,
>>
>> I don't fully understand this docstring. Is it correct that the function
>> will unmap the address range given by `start` and `size`, _and_ free the
>> pages used to hold the mappings at the leaf level of the page table?
>
> If the vma owns a refcount on those pages, then the refcounts are dropped.

Maybe drop the "at the leaf level leaving all other page tables intact".
It confuses me, since when would this not be the case?

How about this:

This clears the virtual memory map for the range given by `start` and
`size`, dropping refcounts to memory held by the mappings in this range. That
is, anonymous memory is completely freed, file-backed memory has its
reference count on page cache folio's dropped, any dirty data will still
be written back to disk as usual.

>
>> > and freeing any memory referenced by the VMA in this range. That is,
>> > +    /// anonymous memory is completely freed, file-backed memory has its reference count on page
>> > +    /// cache folio's dropped, any dirty data will still be written back to disk as usual.
>> > +    #[inline]
>> > +    pub fn zap_page_range_single(&self, address: usize, size: usize) {


Best regards,
Andreas Hindborg