From: Zi Yan <ziy@nvidia.com>
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
akpm@linux-foundation.org, stable@vger.kernel.org,
guoren@kernel.org, huanyi.xj@alibaba-inc.com,
guohanjun@huawei.com, zjb194813@alibaba-inc.com,
tianhu.hh@alibaba-inc.com, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5.15] mm: validate buddy page before using
Date: Mon, 20 Jun 2022 08:25:33 -0400 [thread overview]
Message-ID: <2E1BD795-A6EA-4272-859B-A29DFAF6DC07@nvidia.com> (raw)
In-Reply-To: <d52e17da-a382-0028-2b16-105ab7053028@linux.alibaba.com>
[-- Attachment #1: Type: text/plain, Size: 4276 bytes --]
On 20 Jun 2022, at 8:18, Xianting Tian wrote:
> 在 2022/6/20 下午8:06, Greg KH 写道:
>> On Mon, Jun 20, 2022 at 07:57:05PM +0800, Xianting Tian wrote:
>>> 在 2022/6/20 下午7:42, Greg KH 写道:
>>>> On Mon, Jun 20, 2022 at 06:54:44PM +0800, Xianting Tian wrote:
>>>>> 在 2022/6/20 下午6:17, Greg KH 写道:
>>>>>> On Fri, Jun 17, 2022 at 12:17:45AM +0800, Xianting Tian wrote:
>>>>>>> Commit 787af64d05cd ("mm: page_alloc: validate buddy before check its migratetype.")
>>>>>>> fixes a bug in 1dd214b8f21c and there is a similar bug in d9dddbf55667 that
>>>>>>> can be fixed in a similar way too.
>>>>>>>
>>>>>>> In unset_migratetype_isolate(), we also need the fix, so move page_is_buddy()
>>>>>>> from mm/page_alloc.c to mm/internal.h
>>>>>>>
>>>>>>> In addition, for RISC-V arch the first 2MB RAM could be reserved for opensbi,
>>>>>>> so it would have pfn_base=512 and mem_map began with 512th PFN when
>>>>>>> CONFIG_FLATMEM=y.
>>>>>>> But __find_buddy_pfn algorithm thinks the start pfn 0, it could get 0 pfn or
>>>>>>> less than the pfn_base value. We need page_is_buddy() to verify the buddy to
>>>>>>> prevent accessing an invalid buddy.
>>>>>>>
>>>>>>> Fixes: d9dddbf55667 ("mm/page_alloc: prevent merging between isolated and other pageblocks")
>>>>>>> Cc: stable@vger.kernel.org
>>>>>>> Reported-by: zjb194813@alibaba-inc.com
>>>>>>> Reported-by: tianhu.hh@alibaba-inc.com
>>>>>>> Signed-off-by: Xianting Tian <xianting.tian@linux.alibaba.com>
>>>>>>> ---
>>>>>>> mm/internal.h | 34 ++++++++++++++++++++++++++++++++++
>>>>>>> mm/page_alloc.c | 37 +++----------------------------------
>>>>>>> mm/page_isolation.c | 3 ++-
>>>>>>> 3 files changed, 39 insertions(+), 35 deletions(-)
>>>>>> What is the commit id of this in Linus's tree?
>>>>> It is also this one,
>>>>>
>>>>> commit 787af64d05cd528aac9ad16752d11bb1c6061bb9
>>>>> Author: Zi Yan <ziy@nvidia.com>
>>>>> Date: Wed Mar 30 15:45:43 2022 -0700
>>>>>
>>>>> mm: page_alloc: validate buddy before check its migratetype.
>>>>>
>>>>> Whenever a buddy page is found, page_is_buddy() should be called to
>>>>> check its validity. Add the missing check during pageblock merge check.
>>>>>
>>>>> Fixes: 1dd214b8f21c ("mm: page_alloc: avoid merging non-fallbackable
>>>>> pageblocks with others")
>>>>> Link:
>>>>> https://lore.kernel.org/all/20220330154208.71aca532@gandalf.local.home/
>>>>> Reported-and-tested-by: Steven Rostedt <rostedt@goodmis.org>
>>>>> Signed-off-by: Zi Yan <ziy@nvidia.com>
>>>>> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>>>> This commit looks nothing like what you posted here.
>>>>
>>>> Why the vast difference with no explaination as to why these are so
>>>> different from the other backports you provided here? Also why is the
>>>> subject lines changed?
>>> Yes, the changes of 5.15 are not same with others branches, because we need
>>> additional fix for 5.15,
>>>
>>> You can check it in the thread:
>>>
>>> https://lore.kernel.org/linux-mm/435B45C3-E6A5-43B2-A5A2-318C748691FC@nvidia.com/ <https://lore.kernel.org/linux-mm/435B45C3-E6A5-43B2-A5A2-318C748691FC@nvidia.com/>
>>>
>>> Right. But pfn_valid_within() was removed since 5.15. So your fix is
>>> required for kernels between 5.15 and 5.17 (inclusive).
>> What is "your fix" here?
>>
>> This change differs a lot from what is in Linus's tree now, so this all
>> needs to be resend and fixed up as I mention above if we are going to be
>> able to take this. As-is, it's all not correct so are dropped.
>
> I think, for branches except 5.15, you can just backport Zi Yan's commit 787af64d05cd in Linus tree. I won't send more patches further,
Please do not back port my commit 787af64d05cd directly, because although
it fixes the issue, the code indentation is not right. At least, I tried
to cherry-pick the commit and failed. The commit just happens to fix
the issue in commit d9dddbf55667.
>
> For 5.15, because it need additional fix except commit 787af64d05cd, I will send a new patch as your comments.
>
> Is it ok for you?
>
>>
>> thanks,
>>
>> greg k-h
--
Best Regards,
Yan, Zi
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 854 bytes --]
next prev parent reply other threads:[~2022-06-20 12:25 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 16:17 [PATCH] mm: page_alloc: " Xianting Tian
2022-06-16 16:17 ` [PATCH 4.14] " Xianting Tian
2022-06-16 16:17 ` [PATCH 4.19] " Xianting Tian
2022-06-16 16:17 ` [PATCH 5.4] " Xianting Tian
2022-06-16 16:17 ` [PATCH 5.10] " Xianting Tian
2022-06-16 16:17 ` [PATCH 5.15] mm: " Xianting Tian
2022-06-20 10:17 ` Greg KH
2022-06-20 10:54 ` Xianting Tian
2022-06-20 11:42 ` Greg KH
2022-06-20 11:57 ` Xianting Tian
2022-06-20 12:06 ` Greg KH
2022-06-20 12:18 ` Xianting Tian
2022-06-20 12:24 ` Greg KH
2022-06-20 12:41 ` Xianting Tian
2022-06-20 12:45 ` Zi Yan
2022-06-20 12:54 ` Greg KH
2022-06-20 14:13 ` Zi Yan
2022-06-20 20:31 ` Greg KH
2022-06-22 1:37 ` Xianting Tian
2022-06-22 1:52 ` Zi Yan
2022-07-06 2:51 ` Xianting Tian
2022-06-20 12:25 ` Zi Yan [this message]
2022-06-16 16:17 ` [PATCH 5.17] " Xianting Tian
2022-06-16 16:20 ` [PATCH] mm: page_alloc: " Xianting Tian
2022-06-16 16:50 ` Greg KH
2022-06-17 1:24 ` Xianting Tian
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=2E1BD795-A6EA-4272-859B-A29DFAF6DC07@nvidia.com \
--to=ziy@nvidia.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=guoren@kernel.org \
--cc=huanyi.xj@alibaba-inc.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=stable@vger.kernel.org \
--cc=tianhu.hh@alibaba-inc.com \
--cc=xianting.tian@linux.alibaba.com \
--cc=zjb194813@alibaba-inc.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