The patch titled
Subject: mm-check-for-sigkill-inside-dup_mmap-loop-fix
has been removed from the -mm tree. Its filename was
mm-check-for-sigkill-inside-dup_mmap-loop-fix.patch
This patch was dropped because it was folded into mm-check-for-sigkill-inside-dup_mmap-loop.patch
------------------------------------------------------
From: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
Subject: mm-check-for-sigkill-inside-dup_mmap-loop-fix
add comment
Cc: Alexander Viro <viro@xxxxxxxxxxxxxxxxxx>
Cc: David Rientjes <rientjes@xxxxxxxxxx>
Cc: Kirill A. Shutemov <kirill.shutemov@xxxxxxxxxxxxxxx>
Cc: Michal Hocko <mhocko@xxxxxxxx>
Cc: Rik van Riel <riel@xxxxxxxxxx>
Cc: Tetsuo Handa <penguin-kernel@xxxxxxxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
kernel/fork.c | 3 +++
1 file changed, 3 insertions(+)
diff -puN kernel/fork.c~mm-check-for-sigkill-inside-dup_mmap-loop-fix kernel/fork.c
--- a/kernel/fork.c~mm-check-for-sigkill-inside-dup_mmap-loop-fix
+++ a/kernel/fork.c
@@ -440,6 +440,9 @@ static __latent_entropy int dup_mmap(str
continue;
}
charge = 0;
+ /*
+ * Don't duplicate many vmas if we've been oom-killed
+ */
if (fatal_signal_pending(current)) {
retval = -EINTR;
goto out;
_
Patches currently in -mm which might be from akpm@xxxxxxxxxxxxxxxxxxxx are
fs-ocfs2-adding-new-return-type-vm_fault_t-fix.patch
zram-introduce-zram-memory-tracking-fix.patch
zram-introduce-zram-memory-tracking-update-fix.patch
zram-introduce-zram-memory-tracking-update-fix-fix.patch
mm-check-for-sigkill-inside-dup_mmap-loop.patch
mm-vmalloc-pass-proper-vm_start-into-debugobjects-fix.patch
mm-shmem-make-statst_blksize-return-huge-page-size-if-thp-is-on-fix.patch
mm-ksm-move-page_stable_node-from-ksmh-to-ksmc-fix.patch
list_lru-prefetch-neighboring-list-entries-before-acquiring-lock-fix.patch
mm-oom-cgroup-aware-oom-killer-fix.patch
mm-oom-cgroup-aware-oom-killer-fix-2.patch
mm-oom-docs-describe-the-cgroup-aware-oom-killer-fix-2-fix.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
