From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, yuzhao@google.com, surenb@google.com,
akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: [folded-merged] mm-delete-unused-mmf_oom_victim-flag-fix.patch removed from -mm tree
Date: Mon, 26 Sep 2022 14:04:18 -0700 [thread overview]
Message-ID: <20220926210419.69ACBC433D7@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm-delete-unused-mmf_oom_victim-flag-fix
has been removed from the -mm tree. Its filename was
mm-delete-unused-mmf_oom_victim-flag-fix.patch
This patch was dropped because it was folded into mm-delete-unused-mmf_oom_victim-flag.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-delete-unused-mmf_oom_victim-flag-fix
Date: Sun Sep 18 05:03:09 PM PDT 2022
remove comment about now-removed mm_is_oom_victim()
Cc: Suren Baghdasaryan <surenb@google.com>
Cc: Yu Zhao <yuzhao@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/mmap.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
--- a/mm/mmap.c~mm-delete-unused-mmf_oom_victim-flag-fix
+++ a/mm/mmap.c
@@ -3105,8 +3105,7 @@ void exit_mmap(struct mm_struct *mm)
/*
* Set MMF_OOM_SKIP to hide this task from the oom killer/reaper
- * because the memory has been already freed. Do not bother checking
- * mm_is_oom_victim because setting a bit unconditionally is cheaper.
+ * because the memory has been already freed.
*/
set_bit(MMF_OOM_SKIP, &mm->flags);
mmap_write_lock(mm);
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-delete-unused-mmf_oom_victim-flag.patch
mm-add-merging-after-mremap-resize-checkpatch-fixes.patch
mm-reduce-noise-in-show_mem-for-lowmem-allocations-vs-mapletree.patch
mm-reduce-noise-in-show_mem-for-lowmem-allocations-vs-mapletree-fix.patch
mm-vmscan-fix-a-lot-of-comments-vs-mglru.patch
swap-add-swap_cache_get_folio-fix.patch
memcg-reduce-size-of-memcg-vmstats-structures-fix.patch
mm-damon-vaddr-add-a-comment-for-default-case-in-damon_va_apply_scheme-fix.patch
mm-page_allocc-rename-check_free_page-to-free_page_is_bad.patch
mm-page_allocc-rename-check_free_page-to-free_page_is_bad-fix.patch
mm-page_allocc-document-bulkfree_pcp_prepare-return-value.patch
fs-uninline-inode_maybe_inc_iversion.patch
ipc-msg-mitigate-the-lock-contention-with-percpu-counter-checkpatch-fixes.patch
ipc-msg-mitigate-the-lock-contention-with-percpu-counter-fix-fix.patch
reply other threads:[~2022-09-26 21:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220926210419.69ACBC433D7@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=surenb@google.com \
--cc=yuzhao@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.