linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Michal Hocko <mhocko@suse.com>
Cc: <linux-mm@kvack.org>, Andrew Morton <akpm@linux-foundation.org>,
	"Vlastimil Babka" <vbabka@suse.cz>,
	wangkefeng wang <wangkefeng.wang@huawei.com>
Subject: Re: [RFC PATCH] mm, page_alloc: avoid page_to_pfn() in move_freepages()
Date: Wed, 27 Nov 2019 21:13:00 +0800	[thread overview]
Message-ID: <5d11a679-d822-1c41-8798-1dbb285d3bf6@huawei.com> (raw)
In-Reply-To: <20191127114750.GP20912@dhcp22.suse.cz>



On 2019/11/27 19:47, Michal Hocko wrote:
> On Wed 27-11-19 18:28:00, Kefeng Wang wrote:
>> The start_pfn and end_pfn are already available in move_freepages_block(),
>> pfn_valid_within() should validate pfn first before touching the page,
>> or we might access an unitialized page with CONFIG_HOLES_IN_ZONE configs.
>>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Cc: Michal Hocko <mhocko@suse.com>
>> Cc: Vlastimil Babka <vbabka@suse.cz>
>> Signed-off-by: Kefeng Wang <wangkefeng.wang@huawei.com>
>> ---
>>
>> Here is an oops in 4.4(arm64 enabled CONFIG_HOLES_IN_ZONE),
> 
> Is this reproducible with the current upstream kernel? There were large
> changes in this aread since 4.4

Our inner tester found this oops twice, but couldn't be reproduced for now,
even in 4.4 kernel, still trying...

But the page_to_pfn() shouldn't be used in move_freepages(), right? ; )

> 
> Btw. the below should be part of the changelog.

Ok, will resend.

> 
>> Unable to handle kernel NULL pointer dereference at virtual address 00000000
>> pgd = ffffff8008f7e000
>> [00000000] *pgd=0000000017ffe003, *pud=0000000017ffe003, *pmd=0000000000000000
>> Internal error: Oops: 96000007 [#1] SMP
>> CPU: 0 PID: 0 Comm: swapper/0 Tainted: G        W  O    4.4.185 #1
>>
>> PC is at move_freepages+0x80/0x10c
>> LR is at move_freepages_block+0xd4/0xf4
>> pc : [<ffffff80083332e8>] lr : [<ffffff8008333448>] pstate: 80000085
>> [...]
>> [<ffffff80083332e8>] move_freepages+0x80/0x10c
>> [<ffffff8008333448>] move_freepages_block+0xd4/0xf4
>> [<ffffff8008335414>] __rmqueue+0x2bc/0x44c
>> [<ffffff800833580c>] get_page_from_freelist+0x268/0x600
>> [<ffffff8008335e84>] __alloc_pages_nodemask+0x184/0x88c
>> [<ffffff800837fae8>] new_slab+0xd0/0x494
>> [<ffffff8008381834>] ___slab_alloc.constprop.29+0x1c8/0x2e8
>> [<ffffff80083819a8>] __slab_alloc.constprop.28+0x54/0x84
>> [<ffffff8008381e68>] kmem_cache_alloc+0x64/0x198
>> [<ffffff80085b04e0>] __build_skb+0x44/0xa4
>> [<ffffff80085b06e4>] __netdev_alloc_skb+0xe4/0x134
>>
\



  reply	other threads:[~2019-11-27 13:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-27 10:28 [RFC PATCH] mm, page_alloc: avoid page_to_pfn() in move_freepages() Kefeng Wang
2019-11-27 10:47 ` David Hildenbrand
2019-11-27 11:18   ` [PATCH] " Kefeng Wang
2019-11-27 17:06     ` David Hildenbrand
2019-11-27 11:21   ` [RFC PATCH] " Kefeng Wang
2019-11-27 11:47 ` Michal Hocko
2019-11-27 13:13   ` Kefeng Wang [this message]
2019-11-27 14:13     ` Michal Hocko
2019-11-27 14:28       ` Qian Cai
2019-11-27 14:39       ` Kefeng Wang
2019-11-27 15:09         ` Qian Cai
2019-11-27 17:15       ` David Hildenbrand

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=5d11a679-d822-1c41-8798-1dbb285d3bf6@huawei.com \
    --to=wangkefeng.wang@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=vbabka@suse.cz \
    /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;
as well as URLs for NNTP newsgroup(s).