From: Greg KH <gregkh@linuxfoundation.org>
To: Xianting Tian <xianting.tian@linux.alibaba.com>
Cc: akpm@linux-foundation.org, ziy@nvidia.com,
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 4.9] mm: page_alloc: validate buddy page before using
Date: Mon, 20 Jun 2022 12:17:22 +0200 [thread overview]
Message-ID: <YrBJMtDdslrvUIAW@kroah.com> (raw)
In-Reply-To: <c091b3a2-394a-59b4-dd98-98774e33afea@linux.alibaba.com>
On Fri, Jun 17, 2022 at 04:25:35PM +0800, Xianting Tian wrote:
>
> 在 2022/6/17 下午4:20, Greg KH 写道:
> > On Fri, Jun 17, 2022 at 12:19:28AM +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 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/page_alloc.c | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> > > index a6e682569e5b..1c423faa4b62 100644
> > > --- a/mm/page_alloc.c
> > > +++ b/mm/page_alloc.c
> > > @@ -864,6 +864,9 @@ static inline void __free_one_page(struct page *page,
> > > buddy_idx = __find_buddy_index(page_idx, order);
> > > buddy = page + (buddy_idx - page_idx);
> > > +
> > > + if (!page_is_buddy(page, buddy, order))
> > > + goto done_merging;
> > > buddy_mt = get_pageblock_migratetype(buddy);
> > > if (migratetype != buddy_mt
> > > --
> > > 2.17.1
> > >
> > What is the git commit id of this change in Linus's tree?
>
> It is 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>
>
All now queued up, thanks.
greg k-h
prev parent reply other threads:[~2022-06-20 10:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-16 16:19 Xianting Tian
2022-06-17 8:20 ` Greg KH
2022-06-17 8:25 ` Xianting Tian
2022-06-20 10:17 ` Greg KH [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=YrBJMtDdslrvUIAW@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.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=ziy@nvidia.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