Changes in virt.rs

0326440c3545c86b6501c7c636fcf018d6e87b8c - mm: rename zap_page_range_single() to zap_vma_range()

Fri, 27 Feb 2026 21:08:45 +0100

mm: rename zap_page_range_single() to zap_vma_range()Let's rename it to make it better match our new naming scheme.While at it, polish the kerneldoc.[akpm@linux-foundation.org: fix rustfmtcheck]Link: https://lkml.kernel.org/r/20260227200848.114019-15-david@kernel.orgSigned-off-by: David Hildenbrand (Arm) Reviewed-by: Lorenzo Stoakes (Oracle) Acked-by: Puranjay Mohan Cc: Alexander Gordeev Cc: Alexei Starovoitov Cc: Alice Ryhl Cc: Andrii Nakryiko Cc: Andy Lutomirski Cc: Arnaldo Carvalho de Melo Cc: Arnd Bergmann Cc: Arve Cc: "Borislav Petkov (AMD)" Cc: Carlos Llamas Cc: Christian Borntraeger Cc: Christian Brauner Cc: Claudio Imbrenda Cc: Daniel Borkman Cc: Dave Airlie Cc: David Ahern Cc: David Rientjes Cc: David S. Miller Cc: Dimitri Sivanich Cc: Eric Dumazet Cc: Gerald Schaefer Cc: Greg Kroah-Hartman Cc: Hartley Sweeten Cc: Heiko Carstens Cc: Ian Abbott Cc: Ingo Molnar Cc: Jakub Kacinski Cc: Jani Nikula Cc: Jann Horn Cc: Janosch Frank Cc: Jarkko Sakkinen Cc: Jason Gunthorpe Cc: Jonas Lahtinen Cc: Leon Romanovsky Cc: Liam Howlett Cc: Madhavan Srinivasan Cc: Matthew Wilcox (Oracle) Cc: Michael Ellerman Cc: Michal Hocko Cc: Miguel Ojeda Cc: Mike Rapoport Cc: Namhyung kim Cc: Neal Cardwell Cc: Paolo Abeni Cc: Pedro Falcato Cc: Peter Zijlstra Cc: Rodrigo Vivi Cc: Shakeel Butt Cc: Suren Baghdasaryan Cc: Todd Kjos Cc: Tvrtko Ursulin Cc: Vasily Gorbik Cc: Vincenzo Frascino Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

de008c9ba5684f14e83bcf86cd45fb0e4e6c4d82 - mm/memory: remove "zap_details" parameter from zap_page_range_single()

Fri, 27 Feb 2026 21:08:33 +0100

mm/memory: remove "zap_details" parameter from zap_page_range_single()Nobody except memory.c should really set that parameter to non-NULL. Solet's just drop it and make unmap_mapping_range_vma() usezap_page_range_single_batched() instead.[david@kernel.org: format on a single line] Link: https://lkml.kernel.org/r/8a27e9ac-2025-4724-a46d-0a7c90894ba7@kernel.orgLink: https://lkml.kernel.org/r/20260227200848.114019-3-david@kernel.orgSigned-off-by: David Hildenbrand (Arm) Reviewed-by: Lorenzo Stoakes (Oracle) Acked-by: Puranjay Mohan Cc: Alexander Gordeev Cc: Alexei Starovoitov Cc: Alice Ryhl Cc: Andrii Nakryiko Cc: Andy Lutomirski Cc: Arnaldo Carvalho de Melo Cc: Arnd Bergmann Cc: Arve Cc: "Borislav Petkov (AMD)" Cc: Carlos Llamas Cc: Christian Borntraeger Cc: Christian Brauner Cc: Claudio Imbrenda Cc: Daniel Borkman Cc: Dave Airlie Cc: David Ahern Cc: David Rientjes Cc: David S. Miller Cc: Dimitri Sivanich Cc: Eric Dumazet Cc: Gerald Schaefer Cc: Greg Kroah-Hartman Cc: Hartley Sweeten Cc: Heiko Carstens Cc: Ian Abbott Cc: Ingo Molnar Cc: Jakub Kacinski Cc: Jani Nikula Cc: Jann Horn Cc: Janosch Frank Cc: Jarkko Sakkinen Cc: Jason Gunthorpe Cc: Jonas Lahtinen Cc: Leon Romanovsky Cc: Liam Howlett Cc: Madhavan Srinivasan Cc: Matthew Wilcox (Oracle) Cc: Michael Ellerman Cc: Michal Hocko Cc: Miguel Ojeda Cc: Mike Rapoport Cc: Namhyung kim Cc: Neal Cardwell Cc: Paolo Abeni Cc: Pedro Falcato Cc: Peter Zijlstra Cc: Rodrigo Vivi Cc: Shakeel Butt Cc: Suren Baghdasaryan Cc: Todd Kjos Cc: Tvrtko Ursulin Cc: Vasily Gorbik Cc: Vincenzo Frascino Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

9ea35a25d51b13013b724943a177a7aaf4bfed71 - mm: introduce VMA flags bitmap type

Tue, 25 Nov 2025 11:01:02 +0100

mm: introduce VMA flags bitmap typeIt is useful to transition to using a bitmap for VMA flags so we can avoidrunning out of flags, especially for 32-bit kernels which are constrainedto 32 flags, necessitating some features to be limited to 64-bit kernelsonly.By doing so, we remove any constraint on the number of VMA flags movingforwards no matter the platform and can decide in future to extend beyond64 if required.We start by declaring an opaque types, vma_flags_t (which resemblesmm_struct flags of type mm_flags_t), setting it to precisely the same sizeas vm_flags_t, and place it in union with vm_flags in the VMA declaration.We additionally update struct vm_area_desc equivalently placing the newopaque type in union with vm_flags.This change therefore does not impact the size of struct vm_area_struct orstruct vm_area_desc.In order for the change to be iterative and to avoid impactingperformance, we designate VM_xxx declared bitmap flag values as thosewhich must exist in the first system word of the VMA flags bitmap.We therefore declare vma_flags_clear_all(), vma_flags_overwrite_word(),vma_flags_overwrite_word(), vma_flags_overwrite_word_once(),vma_flags_set_word() and vma_flags_clear_word() in order to allow us toupdate the existing vm_flags_*() functions to utilise these helpers.This is a stepping stone towards converting users to the VMA flags bitmapand behaves precisely as before.By doing this, we can eliminate the existing private vma->__vm_flags fieldin the vma->vm_flags union and replace it with the newly introduced opaquetype vma_flags, which we call flags so we refer to the new bitmap field asvma->flags.We update vma_flag_[test, set]_atomic() to account for the change also.We adapt vm_flags_reset_once() to only clear those bits above the firstsystem word providing write-once semantics to the first system word (whichit is presumed the caller requires - and in all current use cases this isso).As we currently only specify that the VMA flags bitmap size is equal toBITS_PER_LONG number of bits, this is a noop, but is defensive inpreparation for a future change that increases this.We additionally update the VMA userland test declarations to implement thesame changes there.Finally, we update the rust code to reference vma->vm_flags on updaterather than vma->__vm_flags which has been removed. This is safe for now,albeit it is implicitly performing a const cast.Once we introduce flag helpers we can improve this more.No functional change intended.Link: https://lkml.kernel.org/r/bab179d7b153ac12f221b7d65caac2759282cfe9.1764064557.git.lorenzo.stoakes@oracle.comSigned-off-by: Lorenzo Stoakes Acked-by: Vlastimil Babka Reviewed-by: Pedro Falcato Acked-by: Alice Ryhl [rust]Cc: Alex Gaynor Cc: Alistair Popple Cc: Andreas Hindborg Cc: Axel Rasmussen Cc: Baolin Wang Cc: Baoquan He Cc: Barry Song Cc: Ben Segall Cc: Björn Roy Baron Cc: Boqun Feng Cc: Byungchul Park Cc: Chengming Zhou Cc: Chris Li Cc: Danilo Krummrich Cc: David Hildenbrand Cc: David Rientjes Cc: Dev Jain Cc: Dietmar Eggemann Cc: Gary Guo Cc: Gregory Price Cc: "Huang, Ying" Cc: Ingo Molnar Cc: Jann Horn Cc: Jason Gunthorpe Cc: Johannes Weiner Cc: John Hubbard Cc: Joshua Hahn Cc: Juri Lelli Cc: Kairui Song Cc: Kees Cook Cc: Kemeng Shi Cc: Lance Yang Cc: Leon Romanovsky Cc: Liam Howlett Cc: Mathew Brost Cc: Matthew Wilcox (Oracle) Cc: Mel Gorman Cc: Michal Hocko Cc: Miguel Ojeda Cc: Mike Rapoport Cc: Muchun Song Cc: Nhat Pham Cc: Nico Pache Cc: Oscar Salvador Cc: Peter Xu Cc: Peter Zijlstra Cc: Qi Zheng Cc: Rakie Kim Cc: Rik van Riel Cc: Ryan Roberts Cc: Shakeel Butt Cc: Steven Rostedt Cc: Suren Baghdasaryan Cc: Trevor Gross Cc: Valentin Schneider Cc: Vincent Guittot Cc: Wei Xu Cc: xu xin Cc: Yuanchu Xie Cc: Zi Yan Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

5cc5e030bce2ec97ae5cdb2c1b94a98b1047b3fa - rust: mm: mark VmaNew as transparent

Tue, 12 Aug 2025 15:26:56 +0200

rust: mm: mark VmaNew as transparentUnsafe code in VmaNew's methods assumes that the type has the same layoutas the inner `bindings::vm_area_struct`. This is not guaranteed by thedefault struct representation in Rust, but requires specifying the`transparent` representation.Link: https://lkml.kernel.org/r/20250812132712.61007-1-baptiste.lepers@gmail.comFixes: dcb81aeab406 ("mm: rust: add VmaNew for f_ops->mmap()")Signed-off-by: Baptiste Lepers Reviewed-by: Alice Ryhl Cc: Alex Gaynor Cc: Andreas Hindborg Cc: Björn Roy Baron Cc: Boqun Feng Cc: Danilo Krummrich Cc: Gary Guo Cc: Jann Horn Cc: Liam Howlett Cc: Lorenzo Stoakes Cc: Miguel Ojeda Cc: Trevor Gross Cc: Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

5e30550558b1eace5fa4af4e2257216fa8a7c90f - rust: enable `clippy::as_underscore` lint

Sun, 15 Jun 2025 22:55:08 +0200

rust: enable `clippy::as_underscore` lintIn Rust 1.63.0, Clippy introduced the `as_underscore` lint [1]:> The conversion might include lossy conversion or a dangerous cast that> might go undetected due to the type being inferred.>> The lint is allowed by default as using `_` is less wordy than always> specifying the type.Always specifying the type is especially helpful in function callcontexts where the inferred type may change at a distance. Specifyingthe type also allows Clippy to spot more cases of `useless_conversion`.The primary downside is the need to specify the type in trivial getters.There are 4 such functions: 3 have become slightly less ergonomic, 1 wasrevealed to be a `useless_conversion`.While this doesn't eliminate unchecked `as` conversions, it makes suchconversions easier to scrutinize. It also has the slight benefit ofremoving a degree of freedom on which to bikeshed. Thus apply thechanges and enable the lint -- no functional change intended.Link: https://rust-lang.github.io/rust-clippy/master/index.html#as_underscore [1]Reviewed-by: Benno Lossin Reviewed-by: Boqun Feng Signed-off-by: Tamir Duberstein Acked-by: Greg Kroah-Hartman Acked-by: Danilo Krummrich Link: https://lore.kernel.org/r/20250615-ptr-as-ptr-v12-4-f43b024581e8@gmail.com[ Changed `isize` to `c_long`. - Miguel ]Signed-off-by: Miguel Ojeda List of files: /linux/rust/kernel/mm/virt.rs

dcb81aeab406e417bc0b4cf68de6eb07a1d2e6ce - mm: rust: add VmaNew for f_ops->mmap()

Tue, 08 Apr 2025 11:22:43 +0200

mm: rust: add VmaNew for f_ops->mmap()This type will be used when setting up a new vma in an f_ops->mmap() hook.Using a separate type from VmaRef allows us to have a separate set ofoperations that you are only able to use during the mmap() hook. Forexample, the VM_MIXEDMAP flag must not be changed after the initial setupthat happens during the f_ops->mmap() hook.To avoid setting invalid flag values, the methods for clearing VM_MAYWRITEand similar involve a check of VM_WRITE, and return an error if VM_WRITEis set. Trying to use `try_clear_maywrite` without checking the returnvalue results in a compilation error because the `Result` type is marked#[must_use].For now, there's only a method for VM_MIXEDMAP and not VM_PFNMAP. When weadd a VM_PFNMAP method, we will need some way to prevent you from settingboth VM_MIXEDMAP and VM_PFNMAP on the same vma.Link: https://lkml.kernel.org/r/20250408-vma-v16-6-d8b446e885d9@google.comSigned-off-by: Alice Ryhl Acked-by: Lorenzo Stoakes Acked-by: Liam R. Howlett Reviewed-by: Jann Horn Reviewed-by: Andreas Hindborg Cc: Alex Gaynor Cc: Arnd Bergmann Cc: Balbir Singh Cc: Benno Lossin Cc: Björn Roy Baron Cc: Boqun Feng Cc: Gary Guo Cc: Greg Kroah-Hartman Cc: John Hubbard Cc: Matthew Wilcox (Oracle) Cc: Miguel Ojeda Cc: Suren Baghdasaryan Cc: Trevor Gross Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

bf3d331bb80749542cf299f94c471f611fb113b1 - mm: rust: add vm_insert_page

Tue, 08 Apr 2025 11:22:40 +0200

mm: rust: add vm_insert_pageThe vm_insert_page method is only usable on vmas with the VM_MIXEDMAPflag, so we introduce a new type to keep track of such vmas.The approach used in this patch assumes that we will not need to encodemany flag combinations in the type. I don't think we need to encode morethan VM_MIXEDMAP and VM_PFNMAP as things are now. However, if thatbecomes necessary, using generic parameters in a single type would scalebetter as the number of flags increases.Link: https://lkml.kernel.org/r/20250408-vma-v16-3-d8b446e885d9@google.comSigned-off-by: Alice Ryhl Acked-by: Lorenzo Stoakes Acked-by: Liam R. Howlett Reviewed-by: Andreas Hindborg Reviewed-by: Gary Guo Cc: Alex Gaynor Cc: Arnd Bergmann Cc: Balbir Singh Cc: Benno Lossin Cc: Björn Roy Baron Cc: Boqun Feng Cc: Greg Kroah-Hartman Cc: Jann Horn Cc: John Hubbard Cc: Matthew Wilcox (Oracle) Cc: Miguel Ojeda Cc: Suren Baghdasaryan Cc: Trevor Gross Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs

040f404b731207935ed644b14bcc2bb8b8488d00 - mm: rust: add vm_area_struct methods that require read access

Tue, 08 Apr 2025 11:22:39 +0200

mm: rust: add vm_area_struct methods that require read accessThis adds a type called VmaRef which is used when referencing a vma thatyou have read access to. Here, read access means that you hold either themmap read lock or the vma read lock (or stronger).Additionally, a vma_lookup method is added to the mmap read guard, whichenables you to obtain a &VmaRef in safe Rust code.This patch only provides a way to lock the mmap read lock, but a follow-uppatch also provides a way to just lock the vma read lock.Link: https://lkml.kernel.org/r/20250408-vma-v16-2-d8b446e885d9@google.comSigned-off-by: Alice Ryhl Acked-by: Lorenzo Stoakes Acked-by: Liam R. Howlett Reviewed-by: Jann Horn Reviewed-by: Andreas Hindborg Reviewed-by: Gary Guo Cc: Alex Gaynor Cc: Arnd Bergmann Cc: Balbir Singh Cc: Benno Lossin Cc: Björn Roy Baron Cc: Boqun Feng Cc: Greg Kroah-Hartman Cc: John Hubbard Cc: Matthew Wilcox (Oracle) Cc: Miguel Ojeda Cc: Suren Baghdasaryan Cc: Trevor Gross Cc: Vlastimil Babka Signed-off-by: Andrew Morton List of files: /linux/rust/kernel/mm/virt.rs