mm/gup.c: fix typo in comments
Link: https://lkml.kernel.org/r/20230309104813.170309-1-jingyuwang_vip@163.com Signed-off-by: Jingyu Wang <jingyuwang_vip@163.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
This commit is contained in:
parent
5c63a7c32a
commit
5da1a8687a
2
mm/gup.c
2
mm/gup.c
|
@ -2193,7 +2193,7 @@ static bool is_valid_gup_args(struct page **pages, struct vm_area_struct **vmas,
|
||||||
* This does not guarantee that the page exists in the user mappings when
|
* This does not guarantee that the page exists in the user mappings when
|
||||||
* get_user_pages_remote returns, and there may even be a completely different
|
* get_user_pages_remote returns, and there may even be a completely different
|
||||||
* page there in some cases (eg. if mmapped pagecache has been invalidated
|
* page there in some cases (eg. if mmapped pagecache has been invalidated
|
||||||
* and subsequently re faulted). However it does guarantee that the page
|
* and subsequently re-faulted). However it does guarantee that the page
|
||||||
* won't be freed completely. And mostly callers simply care that the page
|
* won't be freed completely. And mostly callers simply care that the page
|
||||||
* contains data that was valid *at some point in time*. Typically, an IO
|
* contains data that was valid *at some point in time*. Typically, an IO
|
||||||
* or similar operation cannot guarantee anything stronger anyway because
|
* or similar operation cannot guarantee anything stronger anyway because
|
||||||
|
|
Loading…
Reference in New Issue