From: Florian Weimer <fw@deneb.enyo.de>
To: Dave Chinner <david@fromorbit.com>
Cc: linux-xfs@vger.kernel.org, linux-fsdevel@vger.kernel.org,
linux-mm@kvack.org
Subject: Re: [bug, 5.2.16] kswapd/compaction null pointer crash [was Re: xfs_inode not reclaimed/memory leak on 5.2.16]
Date: Mon, 30 Sep 2019 23:42:38 +0200 [thread overview]
Message-ID: <87ftkdfokx.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20190930211727.GQ16973@dread.disaster.area> (Dave Chinner's message of "Tue, 1 Oct 2019 07:17:27 +1000")
* Dave Chinner:
>> [ 4001.238446] Call Trace:
>> [ 4001.238450] __reset_isolation_suitable+0x9b/0x120
>> [ 4001.238453] reset_isolation_suitable+0x3b/0x40
>> [ 4001.238456] kswapd+0x98/0x300
>> [ 4001.238460] ? wait_woken+0x80/0x80
>> [ 4001.238463] kthread+0x114/0x130
>> [ 4001.238465] ? balance_pgdat+0x450/0x450
>> [ 4001.238467] ? kthread_park+0x80/0x80
>> [ 4001.238470] ret_from_fork+0x1f/0x30
>
> Ok, so the memory compaction code has had a null pointer dereference
> which has killed kswapd. memory reclaim is going to have serious
> problems from this point on as kswapd does most of the reclaim.
Sorry, no. OpenVPN opened a tun device at the same time (same
second), and udevd reacted to that, but that's it.
I also double-checked, and there haven't been any recent previous
occurrences of that crash.
next prev parent reply other threads:[~2019-09-30 21:44 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 [this message]
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
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=87ftkdfokx.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=david@fromorbit.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-xfs@vger.kernel.org \
/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.