Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751957AbcDRHMv (ORCPT ); Mon, 18 Apr 2016 03:12:51 -0400 Received: from mga02.intel.com ([134.134.136.20]:24208 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750717AbcDRHMu (ORCPT ); Mon, 18 Apr 2016 03:12:50 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,501,1455004800"; d="scan'208";a="947313459" From: "Huang\, Ying" To: Al Viro Cc: "Huang\, Ying" , , LKML Subject: Re: [LKP] [lkp] [parallel lookups machinery, part 2] 96352435af: kernel BUG at mm/slab.c:2599! References: <87k2jvg1yc.fsf@yhuang-dev.intel.com> <20160418015521.GZ25498@ZenIV.linux.org.uk> <87mvorvfbu.fsf@yhuang-dev.intel.com> <20160418021504.GA25498@ZenIV.linux.org.uk> Date: Mon, 18 Apr 2016 15:12:47 +0800 In-Reply-To: <20160418021504.GA25498@ZenIV.linux.org.uk> (Al Viro's message of "Mon, 18 Apr 2016 03:15:04 +0100") Message-ID: <878u0bqtjk.fsf@yhuang-dev.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2113 Lines: 47 Al Viro 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