From: akpm@linux-foundation.org
To: mm-commits@vger.kernel.org, slyfox@gentoo.org, vbabka@suse.cz
Subject: [folded-merged] mm-page_poison-print-page-info-when-corruption-is-caught-v2.patch removed from -mm tree
Date: Thu, 29 Apr 2021 22:22:21 -0700 [thread overview]
Message-ID: <20210430052221.hVDabqUBx%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm-page_poison-print-page-info-when-corruption-is-caught-v2
has been removed from the -mm tree. Its filename was
mm-page_poison-print-page-info-when-corruption-is-caught-v2.patch
This patch was dropped because it was folded into mm-page_poison-print-page-owner-info-when-corruption-is-caught.patch
------------------------------------------------------
From: Sergei Trofimovich <slyfox@gentoo.org>
Subject: mm-page_poison-print-page-info-when-corruption-is-caught-v2
s/dump_page_owner/dump_page/, per Vlastimil
Link: https://lkml.kernel.org/r/20210407230800.1086854-1-slyfox@gentoo.org
Signed-off-by: Sergei Trofimovich <slyfox@gentoo.org>
Acked-by: Vlastimil Babka <vbabka@suse.cz>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_poison.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- a/mm/page_poison.c~mm-page_poison-print-page-info-when-corruption-is-caught-v2
+++ a/mm/page_poison.c
@@ -2,9 +2,9 @@
#include <linux/kernel.h>
#include <linux/string.h>
#include <linux/mm.h>
+#include <linux/mmdebug.h>
#include <linux/highmem.h>
#include <linux/page_ext.h>
-#include <linux/page_owner.h>
#include <linux/poison.h>
#include <linux/ratelimit.h>
#include <linux/kasan.h>
@@ -71,7 +71,7 @@ static void check_poison_mem(struct page
print_hex_dump(KERN_ERR, "", DUMP_PREFIX_ADDRESS, 16, 1, start,
end - start + 1, 1);
dump_stack();
- dump_page_owner(page);
+ dump_page(page, "pagealloc: corrupted page details");
}
static void unpoison_page(struct page *page)
_
Patches currently in -mm which might be from slyfox@gentoo.org are
ia64-drop-unused-ia64_fw_emu-ifdef.patch
ia64-simplify-code-flow-around-swiotlb-init.patch
ia64-fix-efi_debug-build.patch
ia64-mca-always-make-ia64_mca_debug-an-expression.patch
ia64-drop-marked-broken-discontigmem-and-virtual_mem_map.patch
ia64-module-fix-symbolizer-crash-on-fdescr.patch
mm-page_owner-fetch-backtrace-only-for-tracked-pages.patch
mm-page_owner-use-kstrtobool-to-parse-bool-option.patch
mm-page_owner-detect-page_owner-recursion-via-task_struct.patch
mm-page_poison-print-page-owner-info-when-corruption-is-caught.patch
mm-page_alloc-ignore-init_on_free=1-for-debug_pagealloc=1.patch
reply other threads:[~2021-04-30 5:22 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=20210430052221.hVDabqUBx%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=slyfox@gentoo.org \
--cc=vbabka@suse.cz \
/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).