From: akpm@linux-foundation.org
To: akinobu.mita@gmail.com, john.ogness@linutronix.de,
keescook@chromium.org, mm-commits@vger.kernel.org,
pmladek@suse.com, roman.fietze@magna.com, rostedt@goodmis.org,
sergey.senozhatsky@gmail.com, timur@kernel.org
Subject: + mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem.patch added to -mm tree
Date: Sun, 17 Jan 2021 11:33:40 -0800 [thread overview]
Message-ID: <20210117193340.B4Yn3cyZB%akpm@linux-foundation.org> (raw)
The patch titled
Subject: mm/page_poison: use unhashed address in hexdump for check_poison_mem()
has been added to the -mm tree. Its filename is
mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem.patch
This patch should soon appear at
https://ozlabs.org/~akpm/mmots/broken-out/mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem.patch
and later at
https://ozlabs.org/~akpm/mmotm/broken-out/mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem.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: Timur Tabi <timur@kernel.org>
Subject: mm/page_poison: use unhashed address in hexdump for check_poison_mem()
Now that print_hex_dump() is capable of printing unhashed addresses, use
that feature in the code that reports memory errors. Hashed addresses
don't tell you where the corrupted page actually is.
Link: https://lkml.kernel.org/r/20210116220950.47078-3-timur@kernel.org
Signed-off-by: Timur Tabi <timur@kernel.org>
Cc: Akinobu Mita <akinobu.mita@gmail.com>
Cc: John Ogness <john.ogness@linutronix.de>
Cc: Kees Cook <keescook@chromium.org>
Cc: Petr Mladek <pmladek@suse.com>
Cc: Roman Fietze <roman.fietze@magna.com>
Cc: Sergey Senozhatsky <sergey.senozhatsky@gmail.com>
Cc: Steven Rostedt <rostedt@goodmis.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/page_poison.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/mm/page_poison.c~mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem
+++ a/mm/page_poison.c
@@ -67,7 +67,7 @@ static void check_poison_mem(unsigned ch
else
pr_err("pagealloc: memory corruption\n");
- print_hex_dump(KERN_ERR, "", DUMP_PREFIX_ADDRESS, 16, 1, start,
+ print_hex_dump(KERN_ERR, "", DUMP_PREFIX_UNHASHED, 16, 1, start,
end - start + 1, 1);
dump_stack();
}
_
Patches currently in -mm which might be from timur@kernel.org are
lib-hexdump-introduce-dump_prefix_unhashed-for-unhashed-addresses.patch
mm-page_poison-use-unhashed-address-in-hexdump-for-check_poison_mem.patch
reply other threads:[~2021-01-17 19: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=20210117193340.B4Yn3cyZB%akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=akinobu.mita@gmail.com \
--cc=john.ogness@linutronix.de \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=roman.fietze@magna.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky@gmail.com \
--cc=timur@kernel.org \
/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).