From: "Huang\, Ying" <ying.huang@intel.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: "Huang\, Ying" <ying.huang@intel.com>, <lkp@01.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [LKP] [lkp] [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599!
Date: Mon, 18 Apr 2016 15:12:47 +0800 [thread overview]
Message-ID: <878u0bqtjk.fsf@yhuang-dev.intel.com> (raw)
In-Reply-To: <20160418021504.GA25498@ZenIV.linux.org.uk> (Al Viro's message of "Mon, 18 Apr 2016 03:15:04 +0100")
Al Viro <viro@ZenIV.linux.org.uk> writes:
Hi, Viro,
> On Mon, Apr 18, 2016 at 10:08:37AM +0800, Huang, Ying wrote:
>
>> Could you provide a debug branch in your tree for that?
>
> Done - vfs.git#T1 and vfs.git#T2 resp.
The compare result between T1 and T2 is as follow:
=========================================================================================
compiler/kconfig/rootfs/sleep/tbox_group/testcase:
gcc-5/x86_64-allyesdebian/quantal-core-x86_64.cgz/1/vm-vp-quantal-x86_64/boot
commit:
3ab6378a68555a90a11360e2f2d63c9adb4e7101 (T1)
e570d87b645a0bfd80e36df9753faf3598c9fce0 (T2)
3ab6378a68555a90 e570d87b645a0bfd80e36df975
---------------- --------------------------
fail:runs %reproduction fail:runs
| | |
47:47 -100% :3 dmesg.Kernel_panic-not_syncing:Fatal_exception_in_interrupt
47:47 -100% :3 dmesg.RIP:kfree_debugcheck
47:47 -100% :3 dmesg.invalid_opcode:#[##]SMP
47:47 -100% :3 dmesg.kernel_BUG_at_mm/slab.c
7:47 -15% :3 kmsg.APIC_calibration_not_consistent_with_PM-Timer:#ms_instead_of#ms
1:47 -2% :3 kmsg.kfree_debugcheck:out_of_range_ptr#a8h
7:47 -15% :3 kmsg.kfree_debugcheck:out_of_range_ptr#aah
21:47 -45% :3 kmsg.kfree_debugcheck:out_of_range_ptr#ach
1:47 -2% :3 kmsg.kfree_debugcheck:out_of_range_ptr#bah
2:47 -4% :3 kmsg.kfree_debugcheck:out_of_range_ptr#ch
4:47 -9% :3 kmsg.kfree_debugcheck:out_of_range_ptr#eh
11:47 -23% :3 kmsg.kfree_debugcheck:out_of_range_ptr#h
That is, there is same issue for T1, but no such issue for T2.
> How reproducible it is and how certain you are that it's not there on
> the parent commit?
The result is quite stable for tens tests for parents and the first bad
commit.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2016-04-18 7:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-18 1:06 [lkp] [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599! kernel test robot
2016-04-18 1:55 ` Al Viro
2016-04-18 2:08 ` [LKP] " Huang, Ying
2016-04-18 2:15 ` Al Viro
2016-04-18 7:12 ` Huang, Ying [this message]
2016-04-18 11:07 ` Al Viro
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=878u0bqtjk.fsf@yhuang-dev.intel.com \
--to=ying.huang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=viro@ZenIV.linux.org.uk \
/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