linux-kernel - More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Mon, 25 Jul 2016 13:57:00 -0500
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	kernel test robot <xiaolong.ye@...el.com>
Cc:	lkp@...org, containers@...ts.linux-foundation.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: More information please. Re: [fs]  54cc07a761: BUG: kernel test crashed

kernel test robot <xiaolong.ye@...el.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