[PATCH 7/7] mm: Remove can_modify_mm()
From: Pedro Falcato
Date: Tue Aug 06 2024 - 17:30:18 EST
With no more users in the tree, we can finally remove can_modify_mm().
Signed-off-by: Pedro Falcato <pedro.falcato@xxxxxxxxx>
---
mm/internal.h | 8 --------
mm/mseal.c | 21 ---------------------
2 files changed, 29 deletions(-)
diff --git a/mm/internal.h b/mm/internal.h
index 4b516618389..e4416f5da2f 100644
--- a/mm/internal.h
+++ b/mm/internal.h
@@ -1515,8 +1515,6 @@ static inline bool can_modify_vma(struct vm_area_struct *vma)
}
-bool can_modify_mm(struct mm_struct *mm, unsigned long start,
- unsigned long end);
bool can_modify_vma_madv(struct vm_area_struct *vma, int behavior);
#else
static inline int can_do_mseal(unsigned long flags)
@@ -1524,12 +1522,6 @@ static inline int can_do_mseal(unsigned long flags)
return -EPERM;
}
-static inline bool can_modify_mm(struct mm_struct *mm, unsigned long start,
- unsigned long end)
-{
- return true;
-}
-
static inline bool can_modify_vma_madv(struct vm_area_struct *vma, int behavior)
{
return true;
diff --git a/mm/mseal.c b/mm/mseal.c
index fdd1666344f..28cd17d7aaf 100644
--- a/mm/mseal.c
+++ b/mm/mseal.c
@@ -53,27 +53,6 @@ static bool is_ro_anon(struct vm_area_struct *vma)
return false;
}
-/*
- * Check if the vmas of a memory range are allowed to be modified.
- * the memory ranger can have a gap (unallocated memory).
- * return true, if it is allowed.
- */
-bool can_modify_mm(struct mm_struct *mm, unsigned long start, unsigned long end)
-{
- struct vm_area_struct *vma;
-
- VMA_ITERATOR(vmi, mm, start);
-
- /* going through each vma to check. */
- for_each_vma_range(vmi, vma, end) {
- if (unlikely(!can_modify_vma(vma)))
- return false;
- }
-
- /* Allow by default. */
- return true;
-}
-
/*
* Check if a vma is allowed to be modified by madvise.
*/
--
2.46.0