From: Nick Piggin <npiggin@suse.de>
To: Wu Fengguang <fengguang.wu@intel.com>
Cc: Andi Kleen <andi@firstfloor.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: [PATCH] [11/16] HWPOISON: check and isolate corrupted free pages v2
Date: Tue, 9 Jun 2009 15:28:47 +0200 [thread overview]
Message-ID: <20090609132847.GC15219@wotan.suse.de> (raw)
In-Reply-To: <20090609130304.GF5589@localhost>
On Tue, Jun 09, 2009 at 09:03:04PM +0800, Wu Fengguang wrote:
> On Tue, Jun 09, 2009 at 06:02:29PM +0800, Nick Piggin wrote:
> > On Wed, Jun 03, 2009 at 08:46:45PM +0200, Andi Kleen wrote:
> > >
> > > From: Wu Fengguang <fengguang.wu@intel.com>
> > >
> > > If memory corruption hits the free buddy pages, we can safely ignore them.
> > > No one will access them until page allocation time, then prep_new_page()
> > > will automatically check and isolate PG_hwpoison page for us (for 0-order
> > > allocation).
> >
> > It would be kinda nice if this could be done in the handler
> > directly (ie. take the page directly out of the allocator
> > or pcp list). Completely avoiding fastpaths would be a
> > wonderful goal.
>
> In fact Andi have code to do that. We prefer this one because
> - it's simple
> - it's good sanity check for possible software BUGs
> - it mainly adds overhead to high order pages, which is acceptable
Yeah it's not bad. But we don't have much other non-debug options
that check for random memory corruption like this. Given that the
struct page is a very tiny proportion of memory, then I'm not
totally convinced that all this checking in the page allocator is
worthwhile for everyone. It's a much bigger cost if checks and
branches have to be there just for hwpoison.
And I don't think removing a free page from the page allocator is
too much more complex than removing a live page from the pagecache ;)
>
> Thanks,
> Fengguang
>
> > >
> > > + /* Don't complain about poisoned pages */
> > > + if (PageHWPoison(page)) {
> > > + __ClearPageBuddy(page);
> > > + return;
> > > + }
> > > +
>
> I do think the above chunk is not absolutely necessary, though.
>
> Thanks,
> Fengguang
>
>
> > > /*
> > > * Allow a burst of 60 reports, then keep quiet for that minute;
> > > * or allow a steady drip of one report per second.
> > > @@ -650,7 +656,7 @@
> > > /*
> > > * This page is about to be returned from the page allocator
> > > */
> > > -static int prep_new_page(struct page *page, int order, gfp_t gfp_flags)
> > > +static inline int check_new_page(struct page *page)
> > > {
> > > if (unlikely(page_mapcount(page) |
> > > (page->mapping != NULL) |
> > > @@ -659,6 +665,18 @@
> > > bad_page(page);
> > > return 1;
> > > }
> > > + return 0;
> > > +}
> > > +
> > > +static int prep_new_page(struct page *page, int order, gfp_t gfp_flags)
> > > +{
> > > + int i;
> > > +
> > > + for (i = 0; i < (1 << order); i++) {
> > > + struct page *p = page + i;
> > > + if (unlikely(check_new_page(p)))
> > > + return 1;
> > > + }
> > >
> > > set_page_private(page, 0);
> > > set_page_refcounted(page);
--
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 prev parent reply other threads:[~2009-06-09 12:50 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 18:46 [PATCH] [0/16] HWPOISON: Intro Andi Kleen
2009-06-03 18:46 ` [PATCH] [1/16] HWPOISON: Add page flag for poisoned pages Andi Kleen
2009-06-03 18:46 ` [PATCH] [2/16] HWPOISON: Export some rmap vma locking to outside world Andi Kleen
2009-06-03 18:46 ` [PATCH] [3/16] HWPOISON: Add support for poison swap entries v2 Andi Kleen
2009-06-03 18:46 ` [PATCH] [4/16] HWPOISON: Add new SIGBUS error codes for hardware poison signals Andi Kleen
2009-06-03 18:46 ` [PATCH] [5/16] HWPOISON: Add basic support for poisoned pages in fault handler v3 Andi Kleen
2009-06-03 18:46 ` [PATCH] [6/16] HWPOISON: Add various poison checks in mm/memory.c Andi Kleen
2009-06-04 4:26 ` Wu Fengguang
2009-06-04 5:19 ` Andi Kleen
2009-06-04 11:55 ` Wu Fengguang
2009-06-04 12:52 ` Andi Kleen
2009-06-04 12:50 ` Wu Fengguang
2009-06-04 13:02 ` Andi Kleen
2009-06-04 13:16 ` Wu Fengguang
2009-06-09 10:25 ` Nick Piggin
2009-06-09 12:21 ` Wu Fengguang
2009-06-09 12:35 ` Nick Piggin
2009-06-03 18:46 ` [PATCH] [7/16] HWPOISON: x86: Add VM_FAULT_HWPOISON handling to x86 page fault handler v2 Andi Kleen
2009-06-09 9:54 ` Nick Piggin
2009-06-09 12:34 ` [PATCH] HWPOISON: define VM_FAULT_HWPOISON to 0 when feature is disabled Wu Fengguang
2009-06-03 18:46 ` [PATCH] [8/16] HWPOISON: Use bitmask/action code for try_to_unmap behaviour Andi Kleen
2009-06-09 9:57 ` Nick Piggin
2009-06-10 2:27 ` Wu Fengguang
2009-06-10 6:07 ` Nick Piggin
2009-06-03 18:46 ` [PATCH] [9/16] HWPOISON: Handle hardware poisoned pages in try_to_unmap Andi Kleen
2009-06-04 4:35 ` Wu Fengguang
2009-06-04 5:21 ` Andi Kleen
2009-06-03 18:46 ` [PATCH] [10/16] HWPOISON: Handle poisoned pages in set_page_dirty() Andi Kleen
2009-06-04 0:36 ` Wu Fengguang
2009-06-04 5:27 ` Andi Kleen
2009-06-09 9:59 ` Nick Piggin
2009-06-09 12:51 ` Wu Fengguang
2009-06-03 18:46 ` [PATCH] [11/16] HWPOISON: check and isolate corrupted free pages v2 Andi Kleen
2009-06-09 10:02 ` Nick Piggin
2009-06-09 13:03 ` Wu Fengguang
2009-06-09 13:28 ` Nick Piggin [this message]
2009-06-09 13:49 ` Wu Fengguang
2009-06-09 13:55 ` Nick Piggin
2009-06-09 14:56 ` Wu Fengguang
2009-06-09 15:31 ` Nick Piggin
2009-06-03 18:46 ` [PATCH] [12/16] Refactor truncate to allow direct truncating of page Andi Kleen
2009-06-04 4:32 ` Wu Fengguang
2009-06-04 5:20 ` Andi Kleen
2009-06-03 18:46 ` [PATCH] [13/16] HWPOISON: The high level memory error handler in the VM v5 Andi Kleen
2009-06-04 3:24 ` Wu Fengguang
2009-06-04 5:13 ` Andi Kleen
2009-06-04 9:07 ` Wu Fengguang
2009-06-04 9:26 ` Andi Kleen
2009-06-09 9:51 ` Nick Piggin
2009-06-09 11:14 ` Nick Piggin
2009-06-09 10:09 ` Nick Piggin
2009-06-09 16:05 ` Hugh Dickins
2009-06-09 16:35 ` Nick Piggin
2009-06-10 8:38 ` Wu Fengguang
2009-06-10 8:59 ` Nick Piggin
2009-06-10 9:20 ` Wu Fengguang
2009-06-10 11:03 ` Nick Piggin
2009-06-10 12:16 ` Wu Fengguang
2009-06-10 12:36 ` Nick Piggin
2009-06-12 9:58 ` Andi Kleen
2009-06-10 3:10 ` [PATCH] HWPOISON: fix tasklist_lock/anon_vma locking order Wu Fengguang
2009-06-03 18:46 ` [PATCH] [14/16] HWPOISON: FOR TESTING: Enable memory failure code unconditionally Andi Kleen
2009-06-03 18:46 ` [PATCH] [15/16] HWPOISON: Add madvise() based injector for hardware poisoned pages v3 Andi Kleen
2009-06-03 18:46 ` [PATCH] [16/16] HWPOISON: Add simple debugfs interface to inject hwpoison on arbitary PFNs Andi Kleen
2009-06-09 10:20 ` [PATCH] [0/16] HWPOISON: Intro Nick Piggin
2009-06-10 9:07 ` Wu Fengguang
2009-06-10 9:18 ` Nick Piggin
2009-06-10 9:45 ` Wu Fengguang
2009-06-10 11:15 ` Nick Piggin
2009-06-10 12:36 ` Wu Fengguang
2009-06-10 12:47 ` Nick Piggin
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=20090609132847.GC15219@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=fengguang.wu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).