linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Qian Cai <cai@lca.pw>
To: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
Cc: Daniel Jordan <daniel.m.jordan@oracle.com>,
	linux-mm@kvack.org,  mgorman@techsingularity.net, vbabka@suse.cz
Subject: Re: kernel BUG at include/linux/mm.h:1020!
Date: Fri, 22 Mar 2019 09:43:01 -0400	[thread overview]
Message-ID: <1553262181.26196.22.camel@lca.pw> (raw)
In-Reply-To: <CABXGCsMKQfHjOekpbDgNWXNThdBy8UfxxEddEqPMMJZvmygGhQ@mail.gmail.com>

On Fri, 2019-03-22 at 08:41 +0500, Mikhail Gavrilov wrote:
> On Fri, 22 Mar 2019 at 00:14, Qian Cai <cai@lca.pw> wrote:
> > 
> > 
> > That is OK. The above debug patch may still be useful to figure out where
> > those
> > pages come from (or you could add those 3 pages address to the patch as
> > well).
> > They may be initialized in a similar fashion or uninitialized to begin with.
> 
> Strange I modified patch for catch all 0xffffXXXXX07ce000 pages
> 
> diff --git a/mm/page_alloc.c b/mm/page_alloc.c
> index 03fcf73..8808e2a 100644
> --- a/mm/page_alloc.c
> +++ b/mm/page_alloc.c
> @@ -1273,6 +1273,10 @@ static void free_one_page(struct zone *zone,
>  static void __meminit __init_single_page(struct page *page, unsigned long
> pfn,
>   unsigned long zone, int nid)
>  {
> + if (0xffff00000fffffff & page == (void *)0xffff0000007ce000) {
> + printk("KK page = %px\n", page);
> + dump_stack();
> + }
>   mm_zero_struct_page(page);
>   set_page_links(page, zone, nid, pfn);
>   init_page_count(page);

Those pages are not initialized at all which likely mean that memblock did not
even allocate them at the first place, so Mel's patch might work.


  reply	other threads:[~2019-03-22 13:43 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 17:55 Mikhail Gavrilov
2019-03-15 20:58 ` Daniel Jordan
2019-03-15 21:34   ` Qian Cai
2019-03-17 15:22   ` Mel Gorman
2019-03-19 19:14     ` Qian Cai
2019-03-19 19:27       ` Pavel Tatashin
2019-03-19 19:35         ` Qian Cai
2019-03-19 23:13           ` Pavel Tatashin
2019-03-19 23:26             ` Qian Cai
2019-03-20 14:20       ` Mel Gorman
2019-03-20 21:50   ` Mikhail Gavrilov
2019-03-21  5:39     ` Mikhail Gavrilov
2019-03-21 13:21       ` Qian Cai
2019-03-21 15:08         ` Mikhail Gavrilov
2019-03-21 15:48           ` Qian Cai
2019-03-21 18:57             ` Mikhail Gavrilov
2019-03-21 19:14               ` Qian Cai
2019-03-22  3:41                 ` Mikhail Gavrilov
2019-03-22 13:43                   ` Qian Cai [this message]
2019-03-22 11:15       ` Mel Gorman
2019-03-23  4:40         ` Mikhail Gavrilov
2019-03-25 10:58           ` Mel Gorman
2019-03-25 16:06             ` Mikhail Gavrilov
2019-03-25 20:31               ` Mel Gorman
2019-03-26  4:03                 ` Mikhail Gavrilov
2019-03-26 12:03                   ` Mel Gorman
2019-03-27  3:57                     ` Mikhail Gavrilov
2019-03-27  8:54                       ` Mel Gorman
2019-03-22  7:39 ` Oscar Salvador
2019-03-22  7:54   ` Mikhail Gavrilov
2019-03-22  8:55     ` Oscar Salvador
2019-03-22  8:56       ` Oscar Salvador
2019-03-22 17:49         ` Mikhail Gavrilov

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=1553262181.26196.22.camel@lca.pw \
    --to=cai@lca.pw \
    --cc=daniel.m.jordan@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=mikhail.v.gavrilov@gmail.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