* [alternative-merged] mm-mremap-fix-memory-account-on-do_munmap-failure.patch removed from -mm tree
@ 2021-07-21 20:03 akpm
0 siblings, 0 replies; only message in thread
From: akpm @ 2021-07-21 20:03 UTC (permalink / raw)
To: mm-commits, weiyongjun1, wangkefeng.wang, 0x7f454c46, chenwandun
The patch titled
Subject: mm/mremap: fix memory account on do_munmap() failure
has been removed from the -mm tree. Its filename was
mm-mremap-fix-memory-account-on-do_munmap-failure.patch
This patch was dropped because an alternative patch was merged
------------------------------------------------------
From: Chen Wandun <chenwandun@huawei.com>
Subject: mm/mremap: fix memory account on do_munmap() failure
mremap will account the delta between new_len and old_len in
vma_to_resize, and then call move_vma when expanding an existing memory
mapping. In function move_vma, there are two scenarios when calling
do_munmap:
1. move_page_tables from old_addr to new_addr success
2. move_page_tables from old_addr to new_addr fail
In first scenario, it should account old_len if do_munmap fail, because
the delta has already been accounted.
In second scenario, new_addr/new_len will assign to old_addr/old_len if
move_page_table fail, so do_munmap is try to unmap new_addr actually, if
do_munmap fail, it should account the new_len, because error code will be
return from move_vma, and delta will be unaccounted. What'more, because
of new_len == old_len, so account old_len also is OK.
In summary, account old_len will be correct if do_munmap fail.
Link: https://lkml.kernel.org/r/20210717101942.120607-1-chenwandun@huawei.com
Fixes: 51df7bcb6151 ("mm/mremap: account memory on do_munmap() failure")
Signed-off-by: Chen Wandun <chenwandun@huawei.com>
Cc: Dmitry Safonov <0x7f454c46@gmail.com>
Cc: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: Wei Yongjun <weiyongjun1@huawei.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mremap.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/mremap.c~mm-mremap-fix-memory-account-on-do_munmap-failure
+++ a/mm/mremap.c
@@ -686,7 +686,7 @@ static unsigned long move_vma(struct vm_
if (do_munmap(mm, old_addr, old_len, uf_unmap) < 0) {
/* OOM: unable to split vma, just get accounts right */
if (vm_flags & VM_ACCOUNT && !(flags & MREMAP_DONTUNMAP))
- vm_acct_memory(new_len >> PAGE_SHIFT);
+ vm_acct_memory(old_len >> PAGE_SHIFT);
excess = 0;
}
_
Patches currently in -mm which might be from chenwandun@huawei.com are
mm-vmalloc-fix-wrong-behavior-in-vread.patch
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2021-07-21 20:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-07-21 20:03 [alternative-merged] mm-mremap-fix-memory-account-on-do_munmap-failure.patch removed from -mm tree akpm
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).