linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Dave Hansen <dave.hansen@intel.com>
To: Huaitong Han <oenhan@gmail.com>
Cc: "Fengguang Wu" <fengguang.wu@intel.com>,
	linux-mm@kvack.org, "Andrew Morton" <akpm@linux-foundation.org>,
	"Michal Hocko" <mhocko@suse.com>,
	"Jérôme Glisse" <jglisse@redhat.com>,
	"Mel Gorman" <mgorman@techsingularity.net>,
	"Huang Ying" <ying.huang@intel.com>,
	"Ross Zwisler" <ross.zwisler@linux.intel.com>,
	"Minchan Kim" <minchan@kernel.org>,
	"Hugh Dickins" <hughd@google.com>,
	LKML <linux-kernel@vger.kernel.org>,
	lkp@01.org
Subject: Re: BUG: Bad page map in process python2 pte:10000000000 pmd:17e8be067
Date: Thu, 3 May 2018 07:42:57 -0700	[thread overview]
Message-ID: <7d386ba4-85ba-85dd-4f81-4cc984b149dd@intel.com> (raw)
In-Reply-To: <CAAuJbeKT1eBxT4Y8FgQBrQcFDU_3R8ad=s_8zsyj+GPiZT7VhQ@mail.gmail.com>

On 05/02/2018 08:20 PM, Huaitong Han wrote:
> 
> kernel: swap_free: Bad swap file entry 1000000000103256
> kernel: BUG: Bad page map in process in:imjournal  pte:8192b1000 pmd:3ff9324067
> kernel: addr:00007f920adc5000 vm_flags:080000d1 anon_vma:
> (null) mapping:ffff883fe5284960 index:3f8
> kernel: vma->vm_ops->fault: shmem_fault+0x0/0x1d0
> kernel: vma->vm_file->f_op->mmap: shmem_mmap+0x0/0x30
> kernel: CPU: 5 PID: 9166 Comm: in:imjournal Tainted: G        W  OE
> K------------   3.10.0-514.16.1.el7.x86_64 #1

This looks like an entirely different signature.  There are lots of bits
set in the bad swap entry instead of a single one.  It's also a vintage
RHEL kernel, not mainline.

      reply	other threads:[~2018-05-03 14:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19  5:40 Fengguang Wu
2018-04-19 18:53 ` Dave Hansen
2018-05-03  3:20   ` Huaitong Han
2018-05-03 14:42     ` Dave Hansen [this message]

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=7d386ba4-85ba-85dd-4f81-4cc984b149dd@intel.com \
    --to=dave.hansen@intel.com \
    --cc=akpm@linux-foundation.org \
    --cc=fengguang.wu@intel.com \
    --cc=hughd@google.com \
    --cc=jglisse@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lkp@01.org \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=minchan@kernel.org \
    --cc=oenhan@gmail.com \
    --cc=ross.zwisler@linux.intel.com \
    --cc=ying.huang@intel.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