From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
stable@vger.kernel.org, linux-s390 <linux-s390@vger.kernel.org>,
linux-kernel@vger.kernel.org
Cc: Sasha Levin <sashal@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: Re: 4.19.5 and later has tons of false messages "BUG: non-zero pgtables_bytes on freeing mm: -16384"
Date: Thu, 27 Dec 2018 10:28:56 +0100 [thread overview]
Message-ID: <1d6288dd-a65b-463a-8aeb-33904dafa9cc@de.ibm.com> (raw)
In-Reply-To: <4e58571e-1991-4a70-7012-ff9dd76afee3@de.ibm.com>
On 27.12.2018 10:13, Christian Borntraeger wrote:
> Martin,
>
> Right now you get a message
> "BUG: non-zero pgtables_bytes on freeing mm: -16384"
> for EVERY process that exits in 4.19.5 and later.
>
> bisect points to
> commit 4136161d676a93fc8df6bdb80d720c15522d6c24
> Author: Martin Schwidefsky <schwidefsky@de.ibm.com>
> Date: Mon Oct 15 11:09:16 2018 +0200
>
> s390/mm: fix mis-accounting of pgtable_bytes
>
> [ Upstream commit e12e4044aede97974f2222eb7f0ed726a5179a32 ]
>
> Turns out that this patch requires several dependencies so the autoselection of this
> patch was missing that.
>
> Can we either revert this patch or add the dependencies?
>
> Christian
>
It seems that adding
commit 6d212db11947ae5464e4717536ed9faf61c01e86 ("mm: add mm_pxd_folded checks to pgtable_bytes accounting functions")
fixes the issue.
Martin, do we need more?
Christian
next prev parent reply other threads:[~2018-12-27 9:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 9:13 4.19.5 and later has tons of false messages "BUG: non-zero pgtables_bytes on freeing mm: -16384" Christian Borntraeger
2018-12-27 9:28 ` Christian Borntraeger [this message]
2018-12-27 21:01 ` Sasha Levin
2018-12-27 21:06 ` Christian Borntraeger
2018-12-27 22:52 ` Sasha Levin
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=1d6288dd-a65b-463a-8aeb-33904dafa9cc@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=sashal@kernel.org \
--cc=schwidefsky@de.ibm.com \
--cc=stable@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 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).