mm-document-mmu_notifier_invalidate_range_start_nonblock.patch removed from -mm tree
The quilt patch titled
Subject: mm: document mmu_notifier_invalidate_range_start_nonblock()
has been removed from the -mm tree. Its filename was
mm-document-mmu_notifier_invalidate_range_start_nonblock.patch
This patch was dropped because it was merged into the mm-stable branch of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Jann Horn <[email protected]>
Subject: mm: document mmu_notifier_invalidate_range_start_nonblock()
Date: Mon, 18 Sep 2023 22:18:32 +0200
Document what mmu_notifier_invalidate_range_start_nonblock() is for. Also add a __must_check annotation to signal that callers must bail out if a notifier vetoes the operation.
---
include/linux/mmu_notifier.h | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
include/linux/mmu_notifier.h renamed from include/linux/mmu_notifier.h~mm-document-mmu_notifier_invalidate_range_start_nonblock +8 -1
@@ -459,7 +459,14 @@ mmu_notifier_invalidate_range_start(strulock_map_release (&__mmu_notifier_invalidate_range_start_map); } -static inline int +/* +* This version of mmu_notifier_invalidate_range_start() avoids blocking, but it +* can return an error if a notifier can't proceed without blocking, in which +* case you're not allowed to modify PTEs in the specified range. +* +* This is mainly intended for OOM handling. +*/ +static inline int __must_check mmu_notifier_invalidate_range_start_nonblock (struct mmu_notifier_range *range) {int ret =0 ;
_
Patches currently in -mm which might be from [email protected] are