From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id C0DA5C47258 for ; Thu, 25 Jan 2024 12:02:10 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 3F5FD6B0099; Thu, 25 Jan 2024 07:02:10 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 3A67B6B009B; Thu, 25 Jan 2024 07:02:10 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 295BB6B009D; Thu, 25 Jan 2024 07:02:10 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 1A4266B0099 for ; Thu, 25 Jan 2024 07:02:10 -0500 (EST) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id B0217140D0F for ; Thu, 25 Jan 2024 12:02:09 +0000 (UTC) X-FDA: 81717695178.06.D513ED1 Received: from sin.source.kernel.org (sin.source.kernel.org [145.40.73.55]) by imf07.hostedemail.com (Postfix) with ESMTP id 8721640016 for ; Thu, 25 Jan 2024 12:02:07 +0000 (UTC) Authentication-Results: imf07.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=arm.com (policy=none); spf=pass (imf07.hostedemail.com: domain of cmarinas@kernel.org designates 145.40.73.55 as permitted sender) smtp.mailfrom=cmarinas@kernel.org ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1706184128; a=rsa-sha256; cv=none; b=h6rbC6yn8LpErM5WjpytjZWfDkqLynWy38k8cKl6OjmP4JJNxs/A9XuFxnpk0vKdVv1G/i SPa5ZSVBIHzDFXjEuizvzzHF2JoBmYhwiEA2FnUSTvkUkepKgNcrw0OdLMPu1XQXeGe9m0 6rnrOAQ623ECDomwrm5iat3Dblq5cQQ= ARC-Authentication-Results: i=1; imf07.hostedemail.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=arm.com (policy=none); spf=pass (imf07.hostedemail.com: domain of cmarinas@kernel.org designates 145.40.73.55 as permitted sender) smtp.mailfrom=cmarinas@kernel.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1706184128; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=pK/vp4lRx75pY8KWGFMWSlSAfylLRtXK+rvRjQO2H5Q=; b=uDJsCRSbKColsogxwCGgTUJ885RA92eajEjnKTDCMVoP0QswrZX9nikcBD2kGM+gkgOHEA 4UhZ8zn+GOsJerIZWsTCWM6a2Ut2lHFCbusFu+AW0w5GoXbe6JcTV+pwBTuDQb01rMu2Ed r1EibsugtUWnQSOKwfBPrqDw/u+sYV4= Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 42ACFCE27FE; Thu, 25 Jan 2024 12:02:03 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 3D066C433C7; Thu, 25 Jan 2024 12:01:59 +0000 (UTC) Date: Thu, 25 Jan 2024 12:01:56 +0000 From: Catalin Marinas To: kernel test robot Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-kernel@vger.kernel.org, Andrew Morton , Waiman Long , linux-mm@kvack.org Subject: Re: [linus:master] [kmemleak] 39042079a0: kernel-selftests.kvm.memslot_perf_test.fail Message-ID: References: <202401251429.d3dea02b-oliver.sang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <202401251429.d3dea02b-oliver.sang@intel.com> X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 8721640016 X-Stat-Signature: io8matheg6485jzqmq4cqpioz5shnuto X-Rspam-User: X-HE-Tag: 1706184127-349929 X-HE-Meta: U2FsdGVkX18e6Z6fLUvE7HSTWYDpIgOaL2LmQkKt1Gp38MM8NOoRFlExq9wBDEM621B6a6ah+ttdLaZMq+MmPFf4msgqUIuE+RNc7NWAQXPgyekvf5PzX3lAgVOxuctzd55EYR0fuR4T2pUduE3HQ0HhPlUakmYAK1Fpb11/XjMR7UCUXAzVGS4XKY5dy97FL3pFbwZoLEnJ5rywTKXL79Zao9xRFMn0Bp/NzgIhEz+0H+pdGDtN0kiizL8yMvl/4okR0Rgg0E6tlDtsMhsxRFm7CxsmTlgLUaLlj+J8VGvEgl9ZSTacjA+jn/hFhgTKW+HCIr7l9knjS+NOLGMbfIuyZ3vg1P1WtveRYu5wKmFgbt2eTrShS+GPfhedzhMJ6Kd2IppHe7RZJp5x6xyXDdr6QLB9PS6Fe5A3oXmQHPQ/jVZ0SH79FuPTI4YBgkcl5z8Yk+WWpYyAww/MmkXFpGakew7OaPNrrvfLm8kSqIN0wCrCS41w3woEjPLWp5E8dh1khJtQt8Ii/suJ9Eqq8zCO8W8lVv+uhSnW9DrpKQj7FXh8tLng30o59CXYVzIBN7jHEYFxMcSekjqrLj7m8dwf/v7nfcm1fZMxkvO+ZpFCgW77snnfKzKA1w7daLqXMnhsYhwqJCHY0LqFSgbQxJ8QmqM4kbzRoeTlVnzYeHLBtgPhkpRfC/Iq4erPsPqDBEgeUVxbRCo+XGHJZ9/ca+DKSpEkg+Ij74rtIGywcTDHgd8LiRLkenLFAowbDZBLRd6gfOxKW3qJErZkwJweSkdKwnl2CKGv9OxpO6l8XKq/wUOQT32eItbybd9J+I6FuKOwcphiQRb5G2KQj925kQ/e9CFnirfmsUh2T9y1Xu54v6ibZ2gV3tpzJP54YYDYmnOzVzl1ihE6ri/3pSRy6z4e01KwzISbvz+pRC+a753QpU6yRwt5HORlCG5Qa732WiJRr+JAzFZS+slQeBo 7nesxVGY 9fBLiqIgu55UATW+HU/D7y0aNe4wKn9JzS4fzhbJAM4xp24OTtATyB4KfGq0/eXfAGnJphNroMIz6UgqKNMsNzmVsUTBeQ6nqwqEvhk18H7vSO16rEp/8iIQS+zikIWYfxT6KliGxjN72DgpcqMcoyIMuoGIYnhzWm4cphFu9vBdoDtCd7uEe8kt6nYxQrn8kwV5jrahtOb+27UKn2cNNfRosiJYKvDFMUH+IXOTNmYWDDiWfkTamG9A3+CwJmi7rfYz+Lgx6N/y3iEQfNtj2VA9uxCPWov2eH0Z+QnLgV98kQdPL3B9V1txaYjeM9EQm/cZd6TmWcyzYHOs9LykCe7h6VabG5zmP46n3S02W03wIzhL3VTpsyEekq1J2v3NLLLYVVinGZhqdhR98TszO4ILqb2pzAyDg4wir2WavjgfSF+DPXyZzGUggGx3auDDU4KejIeh/1Jiduy6DAamZItUSlTufy0AZ9k4t5ULHRAmh5bQvhzItfvG8HA== X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: List-Subscribe: List-Unsubscribe: On Thu, Jan 25, 2024 at 03:34:37PM +0800, kernel test robot wrote: > kernel test robot noticed "kernel-selftests.kvm.memslot_perf_test.fail" on: > > commit: 39042079a0c241d09fa6fc3bb67c2ddf60011d0f ("kmemleak: avoid RCU stalls when freeing metadata for per-CPU pointers") > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master [...] > The kernel config and materials to reproduce are available at: > https://download.01.org/0day-ci/archive/20240125/202401251429.d3dea02b-oliver.sang@intel.com [...] > # Testing RW performance with 1 runs, 5 seconds each > # > not ok 71 selftests: kvm: memslot_perf_test # TIMEOUT 120 seconds I'm not sure how this relates to kmemleak, especially the commit above. It might as well be that the above kmemleak commit increases the system load and you trip over the timeout above. Is it still reproducible with a larger timeout (unfortunately I don't have the hardware to try to reproduce the problem)? I can see a lockdep warning in the dmesg but that doesn't look related to kmemleak. -- Catalin