fs/dax: NIT fix comment regarding start/end vs range
Fixes: ac46d4f3c432 ("mm/mmu_notifier: use structure for invalidate_range_start/end calls v2") Signed-off-by: Ira Weiny <ira.weiny@intel.com> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
This commit is contained in:
parent
c9aed74e6a
commit
0cefc36b32
2
fs/dax.c
2
fs/dax.c
@ -788,7 +788,7 @@ static void dax_entry_mkclean(struct address_space *mapping, pgoff_t index,
|
|||||||
address = pgoff_address(index, vma);
|
address = pgoff_address(index, vma);
|
||||||
|
|
||||||
/*
|
/*
|
||||||
* Note because we provide start/end to follow_pte_pmd it will
|
* Note because we provide range to follow_pte_pmd it will
|
||||||
* call mmu_notifier_invalidate_range_start() on our behalf
|
* call mmu_notifier_invalidate_range_start() on our behalf
|
||||||
* before taking any lock.
|
* before taking any lock.
|
||||||
*/
|
*/
|
||||||
|
Loading…
x
Reference in New Issue
Block a user