linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wanpeng Li <wanpeng.li@hotmail.com>
To: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] mm/hwpoison: fix fail to split THP w/ refcount held
Date: Mon, 10 Aug 2015 17:15:14 +0800	[thread overview]
Message-ID: <BLU437-SMTP7349274677DC2936F6E47180700@phx.gbl> (raw)
In-Reply-To: <20150810085047.GC21282@hori1.linux.bs1.fc.nec.co.jp>



On 8/10/15 4:50 PM, Naoya Horiguchi wrote:
> On Mon, Aug 10, 2015 at 04:29:18PM +0800, Wanpeng Li wrote:
>> Hi Naoya,
>>
>> On 8/10/15 4:10 PM, Naoya Horiguchi wrote:
>>> On Mon, Aug 10, 2015 at 02:32:30PM +0800, Wanpeng Li wrote:
>>>> THP pages will get a refcount in madvise_hwpoison() w/ MF_COUNT_INCREASED
>>>> flag, however, the refcount is still held when fail to split THP pages.
>>>>
>>>> Fix it by reducing the refcount of THP pages when fail to split THP.
>>>>
>>>> Signed-off-by: Wanpeng Li <wanpeng.li@hotmail.com>
>>> It seems that the same conditional put_page() would be added to
>>> "soft offline: %#lx page already poisoned" branch too, right?
>> PageHWPoison() is just called before the soft_offline_page() in
>> madvise_hwpoion(). I think the PageHWPosion()
>> check in soft_offline_page() makes more sense for the other
>> soft_offline_page() callsites which don't have the
>> refcount held.
> What I am worried is a race like below:
>
>   CPU0                              CPU1
>
>   madvise_hwpoison
>   get_user_pages_fast
>   PageHWPoison check (false)
>                                     memory_failure
>                                     TestSetPageHWPoison
>   soft_offline_page
>   PageHWPoison check (true)
>   return -EBUSY (without put_page)

Indeed, there is a race even through it is rared happen.

>
> It's rare and madvise_hwpoison() is testing feature, so this never causes
> real problems in production systems, so it's not a big deal.
> My suggestion is maybe just for code correctness thing ...

Thanks for your proposal, I will add your suggestion in v2 and post out
after we have a uniform solution for patch 2/2. :)

Regards,
Wanpeng Li

>
> Thanks,
> Naoya Horiguchi

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

      reply	other threads:[~2015-08-10  9:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-10  6:32 Wanpeng Li
2015-08-10  8:10 ` Naoya Horiguchi
2015-08-10  8:29   ` Wanpeng Li
2015-08-10  8:50     ` Naoya Horiguchi
2015-08-10  9:15       ` Wanpeng Li [this message]

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=BLU437-SMTP7349274677DC2936F6E47180700@phx.gbl \
    --to=wanpeng.li@hotmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=n-horiguchi@ah.jp.nec.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