From: Yunfeng Ye <yeyunfeng@huawei.com>
To: David Hildenbrand <david@redhat.com>, <n-horiguchi@ah.jp.nec.com>
Cc: <linux-mm@kvack.org>, <linux-kernel@vger.kernel.org>,
"hushiyuan@huawei.com" <hushiyuan@huawei.com>,
"linfeilong@huawei.com" <linfeilong@huawei.com>
Subject: Re: [PATCH v2] mm/memory-failure.c: replace with page_shift() in add_to_kill()
Date: Tue, 5 Nov 2019 18:18:49 +0800 [thread overview]
Message-ID: <0220b5ff-bc47-9616-3897-52fa1c674487@huawei.com> (raw)
In-Reply-To: <ff090004-2cf7-9c77-9c9e-7fc5aff90d35@redhat.com>
On 2019/11/5 17:50, David Hildenbrand wrote:
> On 05.11.19 10:38, Yunfeng Ye wrote:
>> The function page_shift() is supported after the commit 94ad9338109f
>> ("mm: introduce page_shift()").
>>
>> So replace with page_shift() in add_to_kill() for readability.
>>
>> Signed-off-by: Yunfeng Ye <yeyunfeng@huawei.com>
>> Reviewed-by: David Hildenbrand <david@redhat.com>
>> Acked-by: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
>> ---
>> v1 -> v2:
>> - add Reviewed-by and Acked-by
>
> Note for the future: No need to resend if there were no code/documentation changes. Andrew will apply the tags when picking up the patch.
>
ok, thanks.
>>
>> mm/memory-failure.c | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/mm/memory-failure.c b/mm/memory-failure.c
>> index 3151c87dff73..e48c50cac889 100644
>> --- a/mm/memory-failure.c
>> +++ b/mm/memory-failure.c
>> @@ -326,7 +326,7 @@ static void add_to_kill(struct task_struct *tsk, struct page *p,
>> if (is_zone_device_page(p))
>> tk->size_shift = dev_pagemap_mapping_shift(p, vma);
>> else
>> - tk->size_shift = compound_order(compound_head(p)) + PAGE_SHIFT;
>> + tk->size_shift = page_shift(compound_head(p));
>>
>> /*
>> * Send SIGKILL if "tk->addr == -EFAULT". Also, as
>>
>
>
prev parent reply other threads:[~2019-11-05 10:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 9:38 Yunfeng Ye
2019-11-05 9:50 ` David Hildenbrand
2019-11-05 10:18 ` Yunfeng Ye [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=0220b5ff-bc47-9616-3897-52fa1c674487@huawei.com \
--to=yeyunfeng@huawei.com \
--cc=david@redhat.com \
--cc=hushiyuan@huawei.com \
--cc=linfeilong@huawei.com \
--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