From: Florian Weimer <fw@deneb.enyo.de>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Dave Chinner <david@fromorbit.com>,
linux-mm@kvack.org, Mel Gorman <mgorman@techsingularity.net>
Subject: Re: [bug, 5.2.16] kswapd/compaction null pointer crash [was Re: xfs_inode not reclaimed/memory leak on 5.2.16]
Date: Fri, 18 Oct 2019 19:38:25 +0200 [thread overview]
Message-ID: <87sgnqc5ta.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <3560f07e-03a7-9291-6494-e0580eeaa6bd@suse.cz> (Vlastimil Babka's message of "Wed, 16 Oct 2019 22:03:39 +0200")
* Vlastimil Babka:
> Thanks. Looks like it's indeed here in the page_to_pfn() embedded in the
> clear_pageblock_skip() expansion. We've got a wrong struct page pointer,
> so page_to_section gives us a bogus value, __nr_to_section() a null
> pointer, and __section_mem_map_addr then accesses it.
>
> Hopefully the commit [1] should address the reason why we got a wrong
> page pointer. You could try cherry-picking it to your stable tree, or
> wait until it appears in a (hopefully near) future stable 5.3.y (5.2 is
> EOL, so it won't appear there).
The commit reference appears to be missing. 8->
Due to hardware changes, I've switched back to a distribution kernel
for now, so I won't see the issue in a while even if it is present in
newer kernels, too. Sorry.
next prev parent reply other threads:[~2019-10-18 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 7:28 xfs_inode not reclaimed/memory leak on 5.2.16 Florian Weimer
2019-09-30 8:54 ` Dave Chinner
2019-09-30 19:07 ` Florian Weimer
2019-09-30 21:17 ` [bug, 5.2.16] kswapd/compaction null pointer crash [was Re: xfs_inode not reclaimed/memory leak on 5.2.16] Dave Chinner
2019-09-30 21:42 ` Florian Weimer
2019-10-01 9:10 ` Vlastimil Babka
2019-10-01 19:40 ` Florian Weimer
2019-10-07 13:28 ` Vlastimil Babka
2019-10-07 13:56 ` Vlastimil Babka
2019-10-08 8:52 ` Mel Gorman
2019-10-16 19:38 ` Florian Weimer
2019-10-16 20:03 ` Vlastimil Babka
2019-10-18 17:38 ` Florian Weimer [this message]
2019-10-21 8:13 ` Vlastimil Babka
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=87sgnqc5ta.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=david@fromorbit.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.