From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, surenb@google.com,
rppt@linux.ibm.com, rientjes@google.com,
quic_sudaraja@quicinc.com, anshuman.khandual@arm.com,
akpm@linux-foundation.org, akpm@linux-foundation.org
Subject: + mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix.patch added to -mm tree
Date: Tue, 12 Apr 2022 14:13:48 -0700 [thread overview]
Message-ID: <20220412211349.32585C385A1@smtp.kernel.org> (raw)
The patch titled
Subject: mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix
has been added to the -mm tree. Its filename is
mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix.patch
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 and is updated
there every 3-4 working days
------------------------------------------------------
From: Andrew Morton <akpm@linux-foundation.org>
Subject: mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix
add comment, per David
Cc: Anshuman Khandual <anshuman.khandual@arm.com>
Cc: David Rientjes <rientjes@google.com>
Cc: Mike Rapoport <rppt@linux.ibm.com>
Cc: Sudarshan Rajagopalan <quic_sudaraja@quicinc.com>
Cc: Suren Baghdasaryan <surenb@google.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
--- a/mm/page_alloc.c~mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix
+++ a/mm/page_alloc.c
@@ -2522,6 +2522,10 @@ static int move_freepages(struct zone *z
for (pfn = start_pfn; pfn <= end_pfn;) {
if (!pfn_valid(pfn)) {
+ /*
+ * Pageblock alignment may cause us to try to access
+ * into a hole
+ */
pfn++;
continue;
}
_
Patches currently in -mm which might be from akpm@linux-foundation.org are
mm-page_alloc-check-pfn-is-valid-before-moving-to-freelist-fix.patch
mm.patch
mm-create-new-mm-swaph-header-file-fix.patch
mm-shmem-make-shmem_init-return-void-fix.patch
ksm-count-ksm-merging-pages-for-each-process-fix.patch
mm-memory_hotplug-refactor-hotadd_init_pgdat-and-try_online_node-checkpatch-fixes.patch
proc-fix-dentry-inode-overinstantiating-under-proc-pid-net-checkpatch-fixes.patch
fs-proc-kcorec-remove-check-of-list-iterator-against-head-past-the-loop-body-fix.patch
add-fat-messages-to-printk-index-checkpatch-fixes.patch
linux-next-rejects.patch
mm-oom_killc-fix-vm_oom_kill_table-ifdeffery.patch
reply other threads:[~2022-04-12 21:36 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=20220412211349.32585C385A1@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=anshuman.khandual@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=quic_sudaraja@quicinc.com \
--cc=rientjes@google.com \
--cc=rppt@linux.ibm.com \
--cc=surenb@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 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).