From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, shy828301@gmail.com,
david@redhat.com, akpm@linux-foundation.org,
akpm@linux-foundation.org
Subject: [folded-merged] mm-slightly-clarify-ksm-logic-in-do_swap_page-fix.patch removed from -mm tree
Date: Thu, 24 Mar 2022 17:35:18 -0700 [thread overview]
Message-ID: <20220325003518.B1740C340EC@smtp.kernel.org> (raw)
The patch titled
Subject: mm-slightly-clarify-ksm-logic-in-do_swap_page-fix
has been removed from the -mm tree. Its filename was
mm-slightly-clarify-ksm-logic-in-do_swap_page-fix.patch
This patch was dropped because it was folded into mm-slightly-clarify-ksm-logic-in-do_swap_page.patch
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-slightly-clarify-ksm-logic-in-do_swap_page-fix
fix comment, per David
Cc: David Hildenbrand <david@redhat.com>
Cc: Yang Shi <shy828301@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/memory.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
--- a/mm/memory.c~mm-slightly-clarify-ksm-logic-in-do_swap_page-fix
+++ a/mm/memory.c
@@ -3609,11 +3609,11 @@ vm_fault_t do_swap_page(struct vm_fault
if (swapcache) {
/*
- * Make sure try_to_free_swap or reuse_swap_page or swapoff did
- * not release the swapcache from under us. The page pin, and
- * pte_same test below, are not enough to exclude that. Even if
- * it is still swapcache, we need to check that the page's swap
- * has not changed.
+ * Make sure try_to_free_swap or swapoff did not release the
+ * swapcache from under us. The page pin, and pte_same test
+ * below, are not enough to exclude that. Even if it is still
+ * swapcache, we need to check that the page's swap has not
+ * changed.
*/
if (unlikely(!PageSwapCache(page) ||
page_private(page) != entry.val))
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-slightly-clarify-ksm-logic-in-do_swap_page.patch
mm-huge_memory-remove-stale-locking-logic-from-__split_huge_pmd-fix.patch
mm.patch
mm-mempolicy-convert-from-atomic_t-to-refcount_t-on-mempolicy-refcnt-fix.patch
linux-next-rejects.patch
linux-next-git-rejects.patch
mm-oom_killc-fix-vm_oom_kill_table-ifdeffery.patch
mutex-subsystem-synchro-test-module-fix.patch
kernel-forkc-export-kernel_thread-to-modules.patch
reply other threads:[~2022-03-25 0:35 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=20220325003518.B1740C340EC@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=shy828301@gmail.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.