linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: linux-mm@kvack.org
Cc: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	kirill.shutemov@linux.intel.com, pasha.tatashin@soleen.com
Subject: [PATCH 0/5] Improve page poisoning implementation
Date: Wed,  8 Apr 2020 08:01:43 -0700	[thread overview]
Message-ID: <20200408150148.25290-1-willy@infradead.org> (raw)

From: "Matthew Wilcox (Oracle)" <willy@infradead.org>

I really don't like that this feature is called page poisoning.
We already had something called page poisoning and it's when you detect
a memory error in a page.  This is just uninitialised pages.  I don't
have the time right now to do that renaming, so just fix some of the
other problems I found with the implementation.

This hasn't been checked out by the build-bots yet, so there may be some
missing conversions.

Matthew Wilcox (Oracle) (5):
  mm: Constify a lot of struct page arguments
  mm: Rename PF_POISONED_PAGE to page_poison_check
  mm: Remove casting away of constness
  mm: Check for page poison in both page_to_nid implementations
  mm: Check page poison before finding a head page

 include/linux/mm.h              | 32 +++++++-------
 include/linux/mm_types.h        | 11 +----
 include/linux/mmdebug.h         |  4 +-
 include/linux/page-flags.h      | 74 ++++++++++++++++-----------------
 include/linux/page_owner.h      |  6 +--
 include/linux/page_ref.h        |  4 +-
 include/linux/pageblock-flags.h |  2 +-
 include/linux/pagemap.h         |  4 +-
 include/linux/swap.h            |  2 +-
 mm/debug.c                      |  6 +--
 mm/hugetlb.c                    |  6 +--
 mm/page_alloc.c                 | 12 +++---
 mm/page_owner.c                 |  2 +-
 mm/sparse.c                     |  1 +
 mm/swapfile.c                   |  6 +--
 mm/util.c                       |  6 +--
 16 files changed, 85 insertions(+), 93 deletions(-)

-- 
2.25.1



             reply	other threads:[~2020-04-08 15:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 15:01 Matthew Wilcox [this message]
2020-04-08 15:01 ` [PATCH 1/5] mm: Constify a lot of struct page arguments Matthew Wilcox
2020-04-08 15:14   ` Pavel Tatashin
2020-04-09 14:09   ` Kirill A. Shutemov
2020-04-09 14:15     ` Matthew Wilcox
2020-04-09 14:28       ` Kirill A. Shutemov
2020-04-09 14:32         ` Matthew Wilcox
2020-04-09 14:47           ` Kirill A. Shutemov
2020-04-09 15:00             ` Kirill A. Shutemov
2020-04-09 17:12             ` Jason Gunthorpe
2020-04-09 20:47               ` John Hubbard
2020-04-08 15:01 ` [PATCH 2/5] mm: Rename PF_POISONED_PAGE to page_poison_check Matthew Wilcox
2020-04-08 15:21   ` Pavel Tatashin
2020-04-09 14:14   ` Kirill A. Shutemov
2020-04-08 15:01 ` [PATCH 3/5] mm: Remove casting away of constness Matthew Wilcox
2020-04-08 15:23   ` Pavel Tatashin
2020-04-09 14:19   ` Kirill A. Shutemov
2020-04-08 15:01 ` [PATCH 4/5] mm: Check for page poison in both page_to_nid implementations Matthew Wilcox
2020-04-08 15:24   ` Pavel Tatashin
2020-04-09 14:21   ` Kirill A. Shutemov
2020-04-08 15:01 ` [PATCH 5/5] mm: Check page poison before finding a head page Matthew Wilcox
2020-04-08 15:32   ` Pavel Tatashin
2020-04-09 14:25   ` Kirill A. Shutemov
2020-04-08 15:11 ` [PATCH 0/5] Improve page poisoning implementation Pavel Tatashin
2020-04-09 20:55   ` John Hubbard

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=20200408150148.25290-1-willy@infradead.org \
    --to=willy@infradead.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-mm@kvack.org \
    --cc=pasha.tatashin@soleen.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