From: Vlastimil Babka <vbabka@suse.cz>
To: Yang Shi <yang.shi@linux.alibaba.com>,
mhocko@kernel.org, mgorman@techsingularity.net,
akpm@linux-foundation.org
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [v2 PATCH 1/2] mm: mempolicy: make the behavior consistent when MPOL_MF_MOVE* and MPOL_MF_STRICT were specified
Date: Wed, 17 Jul 2019 12:55:59 +0200 [thread overview]
Message-ID: <7806e608-ffcb-fd56-2e0f-a20bea127f40@suse.cz> (raw)
In-Reply-To: <efe90132-6832-d61a-5d55-d2cc134c7087@linux.alibaba.com>
On 7/16/19 7:18 PM, Yang Shi wrote:
>> I think after your patch, you miss putback_movable_pages() in cases
>> where some were queued, and later the walk returned -EIO. The previous
>> code doesn't miss it, but it's also not obvious due to the multiple if
>> (!err) checks. I would rewrite it some thing like this:
>>
>> if (ret < 0) {
>> putback_movable_pages(&pagelist);
>> err = ret;
>> goto mmap_out; // a new label above up_write()
>> }
>
> Yes, the old code had putback_movable_pages called when !err. But, I
> think that is for error handling of mbind_range() if I understand it
> correctly since if queue_pages_range() returns -EIO (only MPOL_MF_STRICT
> was specified and there was misplaced page) that page list should be
> empty . The old code should checked whether that list is empty or not.
Hm I guess you're right, returning with EIO means nothing was queued.
> So, in the new code I just removed that.
>
>>
>> The rest can have reduced identation now.
>
> Yes, the goto does eliminate the extra indentation.
>
>>
>>> + else {
>>> + err = mbind_range(mm, start, end, new);
>>>
>>> - if (nr_failed && (flags & MPOL_MF_STRICT))
>>> - err = -EIO;
>>> - } else
>>> - putback_movable_pages(&pagelist);
>>> + if (!err) {
>>> + int nr_failed = 0;
>>> +
>>> + if (!list_empty(&pagelist)) {
>>> + WARN_ON_ONCE(flags & MPOL_MF_LAZY);
>>> + nr_failed = migrate_pages(&pagelist, new_page,
>>> + NULL, start, MIGRATE_SYNC,
>>> + MR_MEMPOLICY_MBIND);
>>> + if (nr_failed)
>>> + putback_movable_pages(&pagelist);
>>> + }
>>> +
>>> + if ((ret > 0) ||
>>> + (nr_failed && (flags & MPOL_MF_STRICT)))
>>> + err = -EIO;
>>> + } else
>>> + putback_movable_pages(&pagelist);
>> While at it, IIRC the kernel style says that when the 'if' part uses
>> '{ }' then the 'else' part should as well, and it shouldn't be mixed.
>
> Really? The old code doesn't have '{ }' for else, and checkpatch doesn't
> report any error or warning.
Checkpatch probably doesn't catch it, nor did the reviewers of the older
code. But coding-style.rst says:
Do not unnecessarily use braces where a single statement will do.
...
This does not apply if only one branch of a conditional statement is a
single
statement; in the latter case use braces in both branches:
.. code-block:: c
if (condition) {
do_this();
do_that();
} else {
otherwise();
}
Thanks,
Vlastimil
next prev parent reply other threads:[~2019-07-17 10:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-22 0:20 [v2 PATCH 0/2] mm: mempolicy: fix mbind()'s inconsistent behavior for unmovable pages Yang Shi
2019-06-22 0:20 ` [v2 PATCH 1/2] mm: mempolicy: make the behavior consistent when MPOL_MF_MOVE* and MPOL_MF_STRICT were specified Yang Shi
2019-07-16 8:12 ` Vlastimil Babka
2019-07-16 8:47 ` Vlastimil Babka
2019-07-16 17:19 ` Yang Shi
2019-07-16 17:18 ` Yang Shi
2019-07-17 10:55 ` Vlastimil Babka [this message]
2019-07-17 16:51 ` Yang Shi
2019-06-22 0:20 ` [v2 PATCH 2/2] mm: mempolicy: handle vma with unmovable pages mapped correctly in mbind Yang Shi
2019-07-16 12:07 ` Vlastimil Babka
2019-07-16 17:28 ` Yang Shi
2019-07-17 18:23 ` Yang Shi
2019-07-17 18:39 ` Yang Shi
2019-07-17 18:50 ` Vlastimil Babka
2019-07-17 19:25 ` Yang Shi
2019-07-15 22:22 ` [v2 PATCH 0/2] mm: mempolicy: fix mbind()'s inconsistent behavior for unmovable pages Andrew Morton
2019-07-15 23:51 ` Yang Shi
2019-07-15 23:54 ` 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=7806e608-ffcb-fd56-2e0f-a20bea127f40@suse.cz \
--to=vbabka@suse.cz \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--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