On Wed, Jun 1, 2022 at 3:09 PM Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> wrote: > > > The patch titled > Subject: mm-drop-oom-code-from-exit_mmap-fix > has been added to the -mm mm-unstable branch. Its filename is > mm-drop-oom-code-from-exit_mmap-fix.patch > > This patch will shortly appear at > https://git.kernel.org/pub/scm/linux/kernel/git/akpm/25-new.git/tree/patches/mm-drop-oom-code-from-exit_mmap-fix.patch > > This patch will later appear in the mm-unstable branch at > git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm > > Before you just go and hit "reply", please: > a) Consider who else should be cc'ed > b) Prefer to cc a suitable mailing list as well > c) Ideally: find the original patch on the mailing list and do a > reply-to-all to that, adding suitable additional cc's > > *** Remember to use Documentation/process/submit-checklist.rst when testing your code *** > > The -mm tree is included into linux-next via the mm-everything > branch at git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm > and is updated there every 2-3 working days > > ------------------------------------------------------ > From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Subject: mm-drop-oom-code-from-exit_mmap-fix > Date: Wed Jun 1 03:07:59 PM PDT 2022 > > fix it for presense of mapletree patchset, per Suren Andrew, could we also restore the mmap_lock_read/write retaking? It does make a difference for parallel memory reaping. If you want I can post a v3 with more explanation about that and also a separate patchset applied over maple-tree branch (if you have it separately). Should I? > > Cc: Suren Baghdasaryan <surenb@xxxxxxxxxx> > Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > --- > > mm/mmap.c | 1 - > 1 file changed, 1 deletion(-) > > --- a/mm/mmap.c~mm-drop-oom-code-from-exit_mmap-fix > +++ a/mm/mmap.c > @@ -3215,7 +3215,6 @@ void exit_mmap(struct mm_struct *mm) > > trace_exit_mmap(mm); > __mt_destroy(&mm->mm_mt); > - mm->mmap = NULL; > mmap_write_unlock(mm); > vm_unacct_memory(nr_accounted); > } > _ > > Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are > > mm-oom_killc-fix-vm_oom_kill_table-ifdeffery.patch > mm-page_alloc-remotely-drain-per-cpu-lists-checkpatch-fixes.patch > mm-start-tracking-vmas-with-maple-tree-fix.patch > damon-convert-__damon_va_three_regions-to-use-the-vma-iterator-fix.patch > mm-mmap-use-advanced-maple-tree-api-for-mmap_region-fix-checkpatch-fixes.patch > mm-remove-the-vma-linked-list-fix-fix.patch > mm-handling-non-lru-pages-returned-by-vm_normal_pages-fix.patch > mm-introduce-clear_highpage_tagged-fix.patch > kasan-fix-zeroing-vmalloc-memory-with-hw_tags-fix.patch > mm-drop-oom-code-from-exit_mmap-fix.patch > squashfs-implement-readahead-checkpatch-fixes.patch >
