From: Sasha Levin <sasha.levin@oracle.com>
To: akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
hughd@google.com, mgorman@suse.de,
Sasha Levin <sasha.levin@oracle.com>
Subject: [PATCH 0/5] mm: poison critical mm/ structs
Date: Mon, 29 Sep 2014 21:47:14 -0400 [thread overview]
Message-ID: <1412041639-23617-1-git-send-email-sasha.levin@oracle.com> (raw)
Currently we're seeing a few issues which are unexplainable by looking at the
data we see and are most likely caused by a memory corruption caused
elsewhere.
This is wasting time for folks who are trying to figure out an issue provided
a stack trace that can't really point out the real issue.
This patch introduces poisoning on struct page, vm_area_struct, and mm_struct,
and places checks in busy paths to catch corruption early.
This series was tested, and it detects corruption in vm_area_struct. Right now
I'm working on figuring out the source of the corruption, (which is a long
standing bug) using KASan, but the current code is useful as it is.
Sasha Levin (5):
mm: add poisoning basics
mm: constify dump_page and friends
mm: poison mm_struct
mm: poison vm_area_struct
mm: poison page struct
fs/exec.c | 5 +++++
include/linux/memcontrol.h | 8 ++++----
include/linux/mm.h | 11 ++++++++++-
include/linux/mm_types.h | 18 ++++++++++++++++++
include/linux/mmdebug.h | 24 ++++++++++++++++++++++--
include/linux/page-flags.h | 24 ++++++++++++++++--------
include/linux/page_cgroup.h | 4 ++--
include/linux/poison.h | 6 ++++++
kernel/fork.c | 13 +++++++++++++
lib/Kconfig.debug | 9 +++++++++
mm/debug.c | 22 ++++++++++++++++++----
mm/memcontrol.c | 6 +++---
mm/mmap.c | 21 ++++++++++++++++++++-
mm/nommu.c | 7 +++++++
mm/page_cgroup.c | 4 ++--
mm/vmacache.c | 5 +++++
16 files changed, 160 insertions(+), 27 deletions(-)
--
1.9.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2014-09-30 1:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-30 1:47 Sasha Levin [this message]
2014-09-30 1:47 ` [PATCH 1/5] mm: add poisoning basics Sasha Levin
2014-09-30 1:47 ` [PATCH 2/5] mm: constify dump_page and friends Sasha Levin
2014-09-30 1:47 ` [PATCH 3/5] mm: poison mm_struct Sasha Levin
2014-09-30 1:47 ` [PATCH 4/5] mm: poison vm_area_struct Sasha Levin
2014-09-30 1:47 ` [PATCH 5/5] mm: poison page struct Sasha Levin
2014-10-07 22:02 ` Dave Hansen
2014-10-08 7:10 ` Christoph Lameter
2014-10-08 14:22 ` Sasha Levin
2014-10-01 21:07 ` [PATCH 0/5] mm: poison critical mm/ structs Andrew Morton
2014-10-01 21:39 ` Sasha Levin
2014-10-01 21:48 ` Andrew Morton
2014-10-02 3:51 ` Sasha Levin
2014-10-02 9:23 ` Hugh Dickins
2014-10-02 14:58 ` Sasha Levin
2014-10-07 22:16 ` Dave Hansen
2014-10-08 16:43 ` Sasha Levin
2014-10-02 15:13 ` Dave Jones
2014-10-09 19:11 ` Sasha Levin
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=1412041639-23617-1-git-send-email-sasha.levin@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
/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).