From: ebiederm@xmission.com (Eric W. Biederman)
To: kernel test robot <xiaolong.ye@intel.com>
Cc: lkp@01.org, containers@lists.linux-foundation.org,
LKML <linux-kernel@vger.kernel.org>
Subject: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed
Date: Mon, 25 Jul 2016 13:57:00 -0500 [thread overview]
Message-ID: <877fc9a6mb.fsf@x220.int.ebiederm.org> (raw)
In-Reply-To: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> (kernel test robot's message of "Sun, 24 Jul 2016 05:20:37 +0800")
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?
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.
Eric
next prev parent reply other threads:[~2016-07-25 19:10 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 ` Eric W. Biederman [this message]
2016-07-26 14:35 ` [LKP] More information please. " Fengguang Wu
2016-07-26 14:52 ` 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=877fc9a6mb.fsf@x220.int.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=containers@lists.linux-foundation.org \
--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