mm: document mmu_notifier_invalidate_range_start_nonblock()
Subsystems (2)
PATCH 1/1 mm: document mmu_notifier_invalidate_range_start_nonblock()
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 +8 -1
@@ -459,7 +459,14 @@ mmu_notifier_invalidate_range_start(struct mmu_notifier_range *range)lock_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 ;
base-commit: 6704c78e2963a5682b4ac3c0e609d36f2405cf17
Signature · 1 line
2.42.0.459.ge4e396fd5e-goog
Quoted 8 lines · Jann Horn
Document what
mmu_notifier_invalidate_range_start_nonblock()is for. Also add a__must_checkannotation to signal that callers must bail out if a notifier vetoes the operation.Signed-off-by Jann Horn <[email protected]>--- include/linux/mmu_notifier.h | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)
Jason
Looks good, thanks.
Quoted 31 lines · Jann Horn
Document what
mmu_notifier_invalidate_range_start_nonblock()is for. Also add a__must_checkannotation to signal that callers must bail out if a notifier vetoes the operation.Signed-off-by Jann Horn <[email protected]>--- include/linux/mmu_notifier.h | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-)include/linux/mmu_notifier.h +8
-1@@ -459,7 +459,14 @@ mmu_notifier_invalidate_range_start(struct mmu_notifier_range *range)lock_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 ;base-commit:
6704c78e2963a5682b4ac3c0e609d36f2405cf17
Quoted 6 lines · Jann Horn
Document what
mmu_notifier_invalidate_range_start_nonblock()is for. Also add a__must_checkannotation to signal that callers must bail out if a notifier vetoes the operation.Signed-off-by Jann Horn <[email protected]>---
I'm late but:
Signature · 3 lines
Cheers, David / dhildenb