Commit 33490af3 authored Oct 26, 2018 by Michal Hocko Committed by Linus Torvalds Oct 26, 2018

mm, mmu_notifier: be explicit about range invalition non-blocking mode

If invalidate_range_start() is called for !blocking mode then all
callbacks have to guarantee they will no block/sleep.  The same obviously
applies to invalidate_range_end because this operation pairs with the
former and they are called from the same context.  Make sure this is
appropriately documented.

Link: http://lkml.kernel.org/r/20180827112623.8992-3-mhocko@kernel.org


Signed-off-by: Michal Hocko <mhocko@suse.com>
Reviewed-by: Jerome Glisse <jglisse@redhat.com>
Cc: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Juergen Gross <jgross@suse.com>
Cc: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

parent 15f570bf

include/linux/mmu_notifier.h

+3 −1

Original line number	Diff line number	Diff line
		@@ -153,7 +153,9 @@ struct mmu_notifier_ops {
		*
		* If blockable argument is set to false then the callback cannot
		* sleep and has to return with -EAGAIN. 0 should be returned
		* otherwise.
		* otherwise. Please note that if invalidate_range_start approves
		* a non-blocking behavior then the same applies to
		* invalidate_range_end.
		*
		*/
		int (invalidate_range_start)(struct mmu_notifier mn,

Admin message