linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Eryu Guan <eguan@redhat.com>
To: Balbir Singh <bsingharora@gmail.com>
Cc: "open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
	<linuxppc-dev@lists.ozlabs.org>,
	liwan@redhat.com
Subject: Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host
Date: Thu, 29 Jun 2017 17:04:28 +0800	[thread overview]
Message-ID: <20170629090428.GN23360@eguan.usersys.redhat.com> (raw)
In-Reply-To: <CAKTCnzk8VMN0hBi24vEoNPGvvX-s8uhrjMdn7drQVDUdfA_+Ow@mail.gmail.com>

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

On Thu, Jun 29, 2017 at 06:47:50PM +1000, Balbir Singh wrote:
> On Thu, Jun 29, 2017 at 1:41 PM, Eryu Guan <eguan@redhat.com> wrote:
> > On Thu, Jun 29, 2017 at 03:16:10AM +1000, Balbir Singh wrote:
> >> On Wed, Jun 28, 2017 at 6:32 PM, Eryu Guan <eguan@redhat.com> wrote:
> <snip>
> >> Thanks for the excellent bug report, I am a little lost on the stack
> >> trace, it shows a bad page access that we think is triggered by the
> >> mmap changes? The patch changed the return type to integrate the call
> >> into trace-cmd. Could you point me to the tests that can help
> >> reproduce the crash. Could you also suggest how long to try the test
> >> cases for?
> >
> > Sorry, I should have provided it in the first place. It's as simple as
> > mounting an ext4 filesystem on my test ppc64le host, i.e.
> >
> > mkdir -p /mnt/ext4
> > mkfs -t ext4 -F /dev/sda5
> > mount /dev/sda5 /mnt/ext4
> >
> 
> I tried this test a few times with the kernel and could not reproduce it.

Yes, it's not reproduced on every host, I'm not sure what makes my test
host so unique yet.

> Could you please share the config and compiler details, I'll retry with -rc7.

[root@ibm-p8-03-lp6 ~]# gcc --version
gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-16)
Copyright (C) 2015 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is
NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR
PURPOSE.

[root@ibm-p8-03-lp6 ~]# rpm -q gcc
gcc-4.8.5-16.el7.ppc64le

I attached kernel config file.

> 
> In the meanwhile, does enabling kmemleak, DEBUG_PAGE_ALLOC,
> slub/slab debug, list corruption, etc catch anything at the time of the
> corruption?

OK, I'll retry with a debug kernel and report back.

Thanks,
Eryu

[-- Attachment #2: config-ppc64le.bz2 --]
[-- Type: application/x-bzip2, Size: 32218 bytes --]

  reply	other threads:[~2017-06-29  9:04 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-28  8:32 [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host Eryu Guan
2017-06-28 17:16 ` Balbir Singh
2017-06-29  3:41   ` Eryu Guan
2017-06-29  8:47     ` Balbir Singh
2017-06-29  9:04       ` Eryu Guan [this message]
2017-06-29 10:05       ` Eryu Guan
2017-06-29 11:12         ` Michael Ellerman
2017-06-29 11:39           ` Eryu Guan
2017-06-29 12:06             ` kworker with empty task->cpus_allowed (was Re: [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host) Michael Ellerman
2017-06-29 13:59               ` Eryu Guan
2017-06-29 14:24                 ` Tejun Heo
2017-06-30  1:08                   ` Michael Ellerman
2017-06-30 11:56                     ` Tejun Heo
2017-06-30 10:07                 ` Michael Ellerman
2017-06-30 11:47                   ` Eryu Guan
2017-07-04  6:26                     ` Michael Ellerman
2017-07-04  8:21                       ` Eryu Guan
2017-07-04 11:06                         ` Michael Ellerman
2017-07-04 12:12                           ` Eryu Guan
2017-06-29  4:54 ` [v4.12-rc1 regression] mount ext4 fs results in kernel crash on PPC64le host Michael Ellerman
2017-06-29 10:27 ` Michael Ellerman
2017-06-29 10:33   ` Eryu Guan
2017-06-29 12:13     ` Michael Ellerman

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=20170629090428.GN23360@eguan.usersys.redhat.com \
    --to=eguan@redhat.com \
    --cc=bsingharora@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=liwan@redhat.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;
as well as URLs for NNTP newsgroup(s).