mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Fengguang Wu <fengguang.wu@intel.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: kernel test robot <xiaolong.ye@intel.com>,
	containers@lists.linux-foundation.org, lkp@01.org,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Tue, 26 Jul 2016 22:35:45 +0800	[thread overview]
Message-ID: <20160726143545.GA23656@wfg-t540p.sh.intel.com> (raw)
In-Reply-To: <877fc9a6mb.fsf@x220.int.ebiederm.org>

Hi Eric,

Sorry for the delay!

On Mon, Jul 25, 2016 at 01:57:00PM -0500, Eric W. Biederman wrote:
>kernel test robot <xiaolong.ye@intel.com> writes:
>
>> FYI, we noticed the following commit:
>>
>> https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.git for-testing
>> commit 54cc07a761deb38318aca64ddf07fc45157c85e0 ("fs: Call d_automount with the filesystems creds")
>>
>> in testcase: boot
>>
>> on test machine: 1 threads qemu-system-x86_64 -enable-kvm -cpu Westmere with 320M memory
>>
>> caused below changes:
>>
>>
>> +-------------------------+------------+------------+
>> |                         | 8175435777 | 54cc07a761 |
>> +-------------------------+------------+------------+
>> | boot_successes          | 102        | 16         |
>> | boot_failures           | 0          | 3          |
>> | BUG:kernel_test_crashed | 0          | 3          |
>> | timestamp.last          | 0          | 54.951425  |
>> +-------------------------+------------+------------+
>>
>>
>>
>> [   19.206454] VFS: Warning: trinity-c0 using old stat() call. Recompile your binary.
>>
>> Elapsed time: 70
>> BUG: kernel test crashed
>
>What application generated the line "BUG: kernel test crashed."
>What flavor of crash was this?

It's a simple boot test with a quick trinity run. So there will be
some randomness in this test.

The "BUG: kernel test crashed" means the VM reboots by itself while
the trinity test is running. If the error message is "BUG: kernel boot
crashed" it'd mean VM abnormally reboots before any test is launched.

>Given the last boot test failure that was reported to me was about 10
>commits after the problem commit I unfortunately can't take it at face
>value that the appropriate commit has been pinpointed.
>
>If you could give me enough information to dig into this that would
>be great.  Otherwise I am going to have to proceed forward on the basis
>that this is a testing robot failure, and that the people who maintain
>the testing robot don't care enough to look after it.

I queued more tests in various KVM instances and find the kernel test
crashes can also happen in the parent commit. So it looks like a false
report. Sorry for the noise!

81754357770ebd90  aeaa4a79ff6a5ed912b7362f20
----------------  --------------------------
       fail:runs  %reproduction    fail:runs
           |             |             |
          5:100          0%           5:100   dmesg.BUG:kernel_test_crashed
           :100          1%           1:100   dmesg.Mem-Info
           :100          1%           1:100   dmesg.invoked_oom-killer:gfp_mask=0x
 
Regards,
Fengguang

  reply	other threads:[~2016-07-26 14:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com>
2016-07-23 21:52 ` Eric W. Biederman
2016-07-25 18:57 ` More information please. " Eric W. Biederman
2016-07-26 14:35   ` Fengguang Wu [this message]
2016-07-26 14:52     ` [LKP] " Eric W. Biederman
2016-07-26 15:13       ` Fengguang Wu
2016-07-26 19:50         ` Eric W. Biederman
2016-07-26 21:18           ` Dave Jones
2016-07-26 21:15         ` Dave Jones

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=20160726143545.GA23656@wfg-t540p.sh.intel.com \
    --to=fengguang.wu@intel.com \
    --cc=containers@lists.linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=xiaolong.ye@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

Powered by JetHome