Commit 1ed7293a authored Jan 08, 2019 by Matthew Wilcox Committed by Linus Torvalds Jan 08, 2019

mm/memory.c: initialise mmu_notifier_range correctly

One of the paths in follow_pte_pmd() initialised the mmu_notifier_range
incorrectly.

Link: http://lkml.kernel.org/r/20190103002126.GM6310@bombadil.infradead.org


Fixes: ac46d4f3 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2")
Signed-off-by: Matthew Wilcox <willy@infradead.org>
Tested-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Jérôme Glisse <jglisse@redhat.com>
Cc: John Hubbard <jhubbard@nvidia.com>
Cc: Jan Kara <jack@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

parent aff876dc

mm/memory.c

+2 −2

Original line number	Diff line number	Diff line
		@@ -4099,8 +4099,8 @@ static int __follow_pte_pmd(struct mm_struct *mm, unsigned long address,
		goto out;

		if (range) {
		range->start = address & PAGE_MASK;
		range->end = range->start + PAGE_SIZE;
		mmu_notifier_range_init(range, mm, address & PAGE_MASK,
		(address & PAGE_MASK) + PAGE_SIZE);
		mmu_notifier_invalidate_range_start(range);
		}
		ptep = pte_offset_map_lock(mm, pmd, address, ptlp);