linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: John Hubbard <jhubbard@nvidia.com>
To: Yang Shi <yang.shi@linux.alibaba.com>, <fabecassis@nvidia.com>,
	<mhocko@suse.com>, <cl@linux.com>, <vbabka@suse.cz>,
	<mgorman@techsingularity.net>, <akpm@linux-foundation.org>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
	<stable@vger.kernel.org>
Subject: Re: [v2 PATCH] mm: move_pages: return valid node id in status if the page is already on the target node
Date: Wed, 4 Dec 2019 21:50:37 -0800	[thread overview]
Message-ID: <565bf53f-1a08-d472-30ac-cf9953e1490a@nvidia.com> (raw)
In-Reply-To: <d4935b9f-39ef-fb91-1786-be84784dccd0@nvidia.com>

On 12/4/19 9:44 PM, John Hubbard wrote:
...           */
> 
> Let's change the comment above add_page_for_migration(), to read:
> 
>          /*
>           * Most errors in the page lookup or isolation are not fatal
>           * and we simply report them via the status array. However,
>           * positive error values are fatal.
>           */
> 
> 
>>           err = add_page_for_migration(mm, addr, current_node,
>> -                &pagelist, flags & MPOL_MF_MOVE_ALL);
>> +                &pagelist, flags & MPOL_MF_MOVE_ALL, status,
>> +                i);
>> +
>>           if (!err)
>>               continue;
>> +        /* store_status() failed in add_page_for_migration() */
> 
> ...and let's replace the above line, with the following:
> 

Correction, I experienced a fatal editor copy-paste mistake here. :) I meant to
suggest this:

		/*
		 * add_page_for_migration() experienced a fatal failure (see the
		 * comments in that routine for details).
		 */

> 
> 
>> +        if (err > 0) {
>> +            err = -EFAULT;
>> +            goto out_flush;
>> +        }
>> +
>>           err = store_status(status, i, err, 1);
>>           if (err)
>>               goto out_flush;
>>

thanks,
-- 
John Hubbard
NVIDIA


  reply	other threads:[~2019-12-05  5:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05  4:21 Yang Shi
2019-12-05  5:44 ` John Hubbard
2019-12-05  5:50   ` John Hubbard [this message]
2019-12-05 17:20   ` Yang Shi
2019-12-05  9:42 ` Qian Cai
2019-12-05 17:39   ` Yang Shi
2019-12-05 18:11     ` Qian Cai
2019-12-05 18:17       ` Christopher Lameter
2019-12-05 11:31 ` Michal Hocko
2019-12-05 17:18   ` Yang Shi

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=565bf53f-1a08-d472-30ac-cf9953e1490a@nvidia.com \
    --to=jhubbard@nvidia.com \
    --cc=akpm@linux-foundation.org \
    --cc=cl@linux.com \
    --cc=fabecassis@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=stable@vger.kernel.org \
    --cc=vbabka@suse.cz \
    --cc=yang.shi@linux.alibaba.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