linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Li Wang <liwang@redhat.com>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	Guenter Roeck <linux@roeck-us.net>,
	Janosch Frank <frankja@linux.vnet.ibm.com>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Linux-MM <linux-mm@kvack.org>, liwang <liwang@redhat.com>
Subject: s390: runtime warning about pgtables_bytes
Date: Thu, 11 Oct 2018 18:04:12 +0800	[thread overview]
Message-ID: <CAEemH2eExK_jwOPZDFBZkwABucpZqh+=s+qpN-tFfMzxwo7cZA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 852 bytes --]

Hi,

When running s390 system with LTP/cve-2017-17052.c[1], the following BUG is
came out repeatedly.
I remember this warning start from kernel-4.16.0 and now it still exist in
kernel-4.19-rc7.
Can anyone take a look?

[ 2678.991496] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.001543] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.002453] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.003256] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.013689] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.024647] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.064408] BUG: non-zero pgtables_bytes on freeing mm: 16384
[ 2679.133963] BUG: non-zero pgtables_bytes on freeing mm: 16384

[1]:
https://github.com/linux-test-project/ltp/blob/master/testcases/cve/cve-2017-17052.c

-- 
Regards,
Li Wang

[-- Attachment #2: Type: text/html, Size: 1612 bytes --]

             reply	other threads:[~2018-10-11 10:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-11 10:04 Li Wang [this message]
2018-10-11 13:02 ` Martin Schwidefsky
2018-10-12 15:08   ` Martin Schwidefsky
2018-10-31 19:57     ` Joe Lawrence
2018-11-02  6:49       ` Martin Schwidefsky

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='CAEemH2eExK_jwOPZDFBZkwABucpZqh+=s+qpN-tFfMzxwo7cZA@mail.gmail.com' \
    --to=liwang@redhat.com \
    --cc=frankja@linux.vnet.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=schwidefsky@de.ibm.com \
    /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