All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	Andi Kleen <andi@firstfloor.org>,
	Fengguang Wu <fengguang.wu@intel.com>,
	Tony Luck <tony.luck@intel.com>,
	gong.chen@linux.intel.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 8/10] mm/hwpoison: fix memory failure still hold reference count after unpoison empty zero page
Date: Tue, 27 Aug 2013 07:40:07 +0800	[thread overview]
Message-ID: <20130826234007.GA15608@hacker.(null)> (raw)
In-Reply-To: <20130826163150.72bb773c.akpm@linux-foundation.org>

Hi Andrew,
On Mon, Aug 26, 2013 at 04:31:50PM -0700, Andrew Morton wrote:
>On Tue, 27 Aug 2013 07:26:04 +0800 Wanpeng Li <liwanp@linux.vnet.ibm.com> wrote:
>
>> Hi Naoya,
>> On Mon, Aug 26, 2013 at 11:45:37AM -0400, Naoya Horiguchi wrote:
>> >On Mon, Aug 26, 2013 at 04:46:12PM +0800, Wanpeng Li wrote:
>> >> madvise hwpoison inject will poison the read-only empty zero page if there is 
>> >> no write access before poison. Empty zero page reference count will be increased 
>> >> for hwpoison, subsequent poison zero page will return directly since page has
>> >> already been set PG_hwpoison, however, page reference count is still increased 
>> >> by get_user_pages_fast. The unpoison process will unpoison the empty zero page 
>> >> and decrease the reference count successfully for the fist time, however, 
>> >> subsequent unpoison empty zero page will return directly since page has already 
>> >> been unpoisoned and without decrease the page reference count of empty zero page.
>> >> This patch fix it by decrease page reference count for empty zero page which has 
>> >> already been unpoisoned and page count > 1.
>> >
>> >I guess that fixing on the madvise side looks reasonable to me, because this
>> >refcount mismatch happens only when we poison with madvise(). The root cause
>> >is that we can get refcount multiple times on a page, even if memory_failure()
>> >or soft_offline_page() can do its work only once.
>> >
>> 
>> I think this just happen in read-only before poison case against empty
>> zero page. 
>> 
>> Hi Andrew,
>> 
>> I see you have already merged the patch, which method you prefer? 
>> 
>
>Addressing it within the madvise code does sound more appropriate.  The
>change which
>mm-hwpoison-fix-memory-failure-still-holding-reference-count-after-unpoisoning-empty-zero-page.patch
>makes is pretty darn strange-looking at at least needs a comment
>telling people what it's doing, and why.

Thanks for your great point out. ;-)
I will address it within the madvise code and resend patch 8/10 ~ patch 10/10.

Regards,
Wanpeng Li 

--
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>

  parent reply	other threads:[~2013-08-26 23:40 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-26  8:46 [PATCH v4 1/10] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages Wanpeng Li
2013-08-26  8:46 ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 2/10] mm/hwpoison: don't need to hold compound lock for hugetlbfs page Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 3/10] mm/hwpoison: fix race against poison thp Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 4/10] mm/hwpoison: replacing atomic_long_sub() with atomic_long_dec() Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 5/10] mm/hwpoison: don't set migration type twice to avoid hold heavy contend zone->lock Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 6/10] mm/hwpoison: drop forward reference declarations __soft_offline_page() Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 7/10] mm/hwpoison: add '#' to madvise_hwpoison Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  8:46 ` [PATCH v4 8/10] mm/hwpoison: fix memory failure still hold reference count after unpoison empty zero page Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26 15:45   ` Naoya Horiguchi
2013-08-26 15:45     ` Naoya Horiguchi
2013-08-26 23:26     ` Wanpeng Li
2013-08-27  0:12       ` Naoya Horiguchi
2013-08-27  0:12         ` Naoya Horiguchi
2013-08-27  0:21         ` Wanpeng Li
2013-08-27  0:21         ` Wanpeng Li
     [not found]         ` <521bf0fc.4950320a.76ab.0f2dSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27  0:46           ` Naoya Horiguchi
2013-08-27  0:46             ` Naoya Horiguchi
2013-08-27  1:17             ` Wanpeng Li
2013-08-27  1:17             ` Wanpeng Li
     [not found]             ` <521bfe37.83892b0a.1b94.2e7cSMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-27  1:34               ` Naoya Horiguchi
2013-08-27  1:34                 ` Naoya Horiguchi
2013-08-27  1:48                 ` Wanpeng Li
2013-08-27  1:48                 ` Wanpeng Li
2013-08-26 23:26     ` Wanpeng Li
     [not found]     ` <521be416.a5e8420a.6786.09d1SMTPIN_ADDED_BROKEN@mx.google.com>
2013-08-26 23:31       ` Andrew Morton
2013-08-26 23:31         ` Andrew Morton
2013-08-26 23:40         ` Wanpeng Li
2013-08-26 23:40         ` Wanpeng Li [this message]
2013-08-26  8:46 ` [PATCH v4 9/10] mm/hwpoison: change permission of corrupt-pfn/unpoison-pfn to 0400 Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-26  9:08   ` Wanpeng Li
2013-08-26  9:08   ` Wanpeng Li
2013-08-26 15:47     ` Naoya Horiguchi
2013-08-26 15:47       ` Naoya Horiguchi
2013-08-26  8:46 ` [PATCH v4 10/10] mm/hwpoison: fix bug triggered by unpoison empty zero page Wanpeng Li
2013-08-26  8:46   ` Wanpeng Li
2013-08-29  6:00 ` [PATCH v4 1/10] mm/hwpoison: fix lose PG_dirty flag for errors on mlocked pages Andi Kleen
2013-08-29  6:00   ` Andi Kleen
2013-08-29  6:17   ` Wanpeng Li
2013-08-29  6:17   ` Wanpeng Li

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='20130826234007.GA15608@hacker.(null)' \
    --to=liwanp@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=fengguang.wu@intel.com \
    --cc=gong.chen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=tony.luck@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.