linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Dufour <ldufour@linux.vnet.ibm.com>
To: Balbir Singh <bsingharora@gmail.com>,
	Michal Hocko <mhocko@kernel.org>,
	Andi Kleen <andi@firstfloor.org>,
	Johannes Weiner <hannes@cmpxchg.org>
Cc: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	akpm@linux-foundation.org,
	Vladimir Davydov <vdavydov.dev@gmail.com>
Subject: Re: [PATCH v2 1/2] mm: Uncharge poisoned pages
Date: Mon, 8 May 2017 12:42:28 +0200	[thread overview]
Message-ID: <03a7ec34-106e-3eb6-0b05-f77a40a2d6b9@linux.vnet.ibm.com> (raw)
In-Reply-To: <1493860869.8082.1.camel@gmail.com>

On 04/05/2017 03:21, Balbir Singh wrote:
>> @@ -5527,7 +5527,7 @@ static void uncharge_list(struct list_head *page_list)
>>  		next = page->lru.next;
>>  
>>  		VM_BUG_ON_PAGE(PageLRU(page), page);
>> -		VM_BUG_ON_PAGE(page_count(page), page);
>> +		VM_BUG_ON_PAGE(!PageHWPoison(page) && page_count(page), page);
>>  
>>  		if (!page->mem_cgroup)
>>  			continue;
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index 8a6bd3a9eb1e..4497d9619bb4 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -541,6 +541,13 @@ static int delete_from_lru_cache(struct page *p)
>>  		 */
>>  		ClearPageActive(p);
>>  		ClearPageUnevictable(p);
>> +
>> +		/*
>> +		 * Poisoned page might never drop its ref count to 0 so we have to
>> +		 * uncharge it manually from its memcg.
>> +		 */
>> +		mem_cgroup_uncharge(p);
>> +
> 
> Yep, that is the right fix
> 
> https://lkml.org/lkml/2017/4/26/133

Sorry Balbir,

You pointed this out since the beginning but I missed your comment.
My mistake.

Thanks,
Laurent.

--
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:[~2017-05-08 10:42 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-25 14:27 [PATCH v2 0/2] BUG raised when onlining HWPoisoned page Laurent Dufour
2017-04-25 14:27 ` [PATCH v2 1/2] mm: Uncharge poisoned pages Laurent Dufour
2017-04-25 23:48   ` Naoya Horiguchi
2017-04-26  1:54   ` Balbir Singh
2017-04-26  2:34     ` Naoya Horiguchi
2017-04-26  3:45       ` Balbir Singh
2017-04-26  4:46         ` Naoya Horiguchi
2017-04-26  8:59           ` Balbir Singh
2017-04-28  9:32             ` Laurent Dufour
2017-04-27 14:37   ` Michal Hocko
2017-04-27 20:51     ` Andi Kleen
2017-04-28  6:07       ` Michal Hocko
2017-04-28  7:31         ` Michal Hocko
2017-04-28  9:17           ` Laurent Dufour
2017-04-28 13:48             ` Michal Hocko
2017-05-02 14:59               ` Laurent Dufour
2017-05-02 18:55                 ` Michal Hocko
2017-05-03 11:34                   ` Laurent Dufour
2017-05-04  1:21                   ` Balbir Singh
2017-05-08 10:42                     ` Laurent Dufour [this message]
2017-05-09  1:41                       ` Balbir Singh
2017-05-08  2:58                   ` Naoya Horiguchi
2017-05-09  9:18                     ` Michal Hocko
2017-05-09 22:59                       ` Naoya Horiguchi
2017-04-25 14:27 ` [PATCH v2 2/2] mm: skip HWPoisoned pages when onlining pages Laurent Dufour
2017-04-26  2:10   ` Balbir Singh
2017-04-26  3:13     ` Naoya Horiguchi
2017-04-28  2:51       ` Balbir Singh
2017-04-28  6:30       ` Michal Hocko
2017-04-28  6:50         ` Michal Hocko
2017-04-28  6:51           ` Michal Hocko
2017-05-10  7:41             ` Michal Hocko
2018-01-17 23:03         ` Andrew Morton
2018-01-23 18:15           ` Laurent Dufour

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=03a7ec34-106e-3eb6-0b05-f77a40a2d6b9@linux.vnet.ibm.com \
    --to=ldufour@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=andi@firstfloor.org \
    --cc=bsingharora@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@kernel.org \
    --cc=n-horiguchi@ah.jp.nec.com \
    --cc=vdavydov.dev@gmail.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