From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm-aS9lmoZGLiVWk0Htik3J/w@public.gmane.org (Eric W. Biederman) Subject: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed Date: Mon, 25 Jul 2016 13:57:00 -0500 Message-ID: <877fc9a6mb.fsf@x220.int.ebiederm.org> References: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> (kernel test robot's message of "Sun, 24 Jul 2016 05:20:37 +0800") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org Errors-To: containers-bounces-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org To: kernel test robot Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org, lkp-JC7UmRfGjtg@public.gmane.org, LKML List-Id: containers.vger.kernel.org kernel test robot 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Content-Type: multipart/mixed; boundary="===============9119625704290575464==" MIME-Version: 1.0 From: Eric W. Biederman To: lkp@lists.01.org Subject: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed Date: Mon, 25 Jul 2016 13:57:00 -0500 Message-ID: <877fc9a6mb.fsf@x220.int.ebiederm.org> In-Reply-To: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> List-Id: --===============9119625704290575464== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable kernel test robot writes: > FYI, we noticed the following commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/ebiederm/user-namespace.g= it for-testing > commit 54cc07a761deb38318aca64ddf07fc45157c85e0 ("fs: Call d_automount wi= th the filesystems creds") > > in testcase: boot > > on test machine: 1 threads qemu-system-x86_64 -enable-kvm -cpu Westmere w= ith 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 --===============9119625704290575464==-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753289AbcGYTKE (ORCPT ); Mon, 25 Jul 2016 15:10:04 -0400 Received: from out03.mta.xmission.com ([166.70.13.233]:54957 "EHLO out03.mta.xmission.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752176AbcGYTKB (ORCPT ); Mon, 25 Jul 2016 15:10:01 -0400 From: ebiederm@xmission.com (Eric W. Biederman) To: kernel test robot Cc: lkp@01.org, containers@lists.linux-foundation.org, LKML References: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> Date: Mon, 25 Jul 2016 13:57:00 -0500 In-Reply-To: <5793dfa5.mvXPj4LJOS0dlz3i%xiaolong.ye@intel.com> (kernel test robot's message of "Sun, 24 Jul 2016 05:20:37 +0800") Message-ID: <877fc9a6mb.fsf@x220.int.ebiederm.org> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-XM-SPF: eid=1bRlGJ-0000t0-0w;;;mid=<877fc9a6mb.fsf@x220.int.ebiederm.org>;;;hst=in02.mta.xmission.com;;;ip=67.3.204.119;;;frm=ebiederm@xmission.com;;;spf=neutral X-XM-AID: U2FsdGVkX1/wKHsRWL8Q0YUxoy4KGksU/kgqqGfFwJA= X-SA-Exim-Connect-IP: 67.3.204.119 X-SA-Exim-Mail-From: ebiederm@xmission.com X-Spam-Report: * -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP * 0.7 XMSubLong Long Subject * 0.0 TVD_RCVD_IP Message was received from an IP address * 0.8 BAYES_50 BODY: Bayes spam probability is 40 to 60% * [score: 0.5000] * -0.0 DCC_CHECK_NEGATIVE Not listed in DCC * [sa07 1397; Body=1 Fuz1=1 Fuz2=1] X-Spam-DCC: XMission; sa07 1397; Body=1 Fuz1=1 Fuz2=1 X-Spam-Combo: ;kernel test robot X-Spam-Relay-Country: X-Spam-Timing: total 310 ms - load_scoreonly_sql: 0.03 (0.0%), signal_user_changed: 3.5 (1.1%), b_tie_ro: 2.6 (0.8%), parse: 0.66 (0.2%), extract_message_metadata: 12 (3.8%), get_uri_detail_list: 1.31 (0.4%), tests_pri_-1000: 4.5 (1.5%), tests_pri_-950: 1.15 (0.4%), tests_pri_-900: 0.97 (0.3%), tests_pri_-400: 25 (8.1%), check_bayes: 24 (7.7%), b_tokenize: 8 (2.5%), b_tok_get_all: 8 (2.6%), b_comp_prob: 2.7 (0.9%), b_tok_touch_all: 3.3 (1.1%), b_finish: 0.70 (0.2%), tests_pri_0: 255 (82.3%), check_dkim_signature: 0.68 (0.2%), check_dkim_adsp: 3.6 (1.2%), tests_pri_500: 4.5 (1.5%), rewrite_mail: 0.00 (0.0%) Subject: More information please. Re: [fs] 54cc07a761: BUG: kernel test crashed X-Spam-Flag: No X-SA-Exim-Version: 4.2.1 (built Thu, 05 May 2016 13:38:54 -0600) X-SA-Exim-Scanned: Yes (on in02.mta.xmission.com) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org kernel test robot 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