All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikhail Gavrilov <mikhail.v.gavrilov@gmail.com>
To: Qian Cai <cai@lca.pw>
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: Thu, 21 Mar 2019 23:57:19 +0500	[thread overview]
Message-ID: <CABXGCsMQ7x2XxJmmsZ_cdcvqsfjqOgYFu40gTAcVOZgf4x6rVQ@mail.gmail.com> (raw)
In-Reply-To: <1553183333.26196.15.camel@lca.pw>

On Thu, 21 Mar 2019 at 20:48, Qian Cai <cai@lca.pw> wrote:
> OK, those pages look similar enough. If you add this to __init_single_page() in
> mm/page_alloc.c :
>
> if (page == (void *)0xffffdcd2607ce000 || page == (void *)0xffffe4b7607ce000 ||
> page == (void *)0xffffd27aa07ce000 || page == (void *)0xffffcf49607ce000) {
>         printk("KK page = %px\n", page);
>         dump_stack();
> }
>
> to see where those pages have been initialized in the first place.

In the new kernel panics "page" also does not repeated.

$ journalctl | grep "page:"
Mar 21 20:46:56 localhost.localdomain kernel: page:fffffbbbe07ce000 is
uninitialized and poisoned
Mar 21 21:28:03 localhost.localdomain kernel: page:ffffdecc207ce000 is
uninitialized and poisoned
Mar 21 23:43:24 localhost.localdomain kernel: page:fffff91ce07ce000 is
uninitialized and poisoned


--
Best Regards,
Mike Gavrilov.


  reply	other threads:[~2019-03-21 18:57 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-12 17:55 kernel BUG at include/linux/mm.h:1020! 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 [this message]
2019-03-21 19:14               ` Qian Cai
2019-03-22  3:41                 ` Mikhail Gavrilov
2019-03-22 13:43                   ` Qian Cai
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=CABXGCsMQ7x2XxJmmsZ_cdcvqsfjqOgYFu40gTAcVOZgf4x6rVQ@mail.gmail.com \
    --to=mikhail.v.gavrilov@gmail.com \
    --cc=cai@lca.pw \
    --cc=daniel.m.jordan@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.