Received-SPF: pass (google.com: domain of linux-kernel+bounces-38559-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
Date: Thu, 25 Jan 2024 12:01:56 +0000
From: Catalin Marinas <catalin.marinas@arm.com>
To: kernel test robot <oliver.sang@intel.com>
Cc: oe-lkp@lists.linux.dev, lkp@intel.com, linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Waiman Long <longman@redhat.com>, linux-mm@kvack.org
Subject: Re: [linus:master] [kmemleak]  39042079a0:
 kernel-selftests.kvm.memslot_perf_test.fail
Message-ID: <ZbJNtFO_N4pVuEUK@arm.com>
References: <202401251429.d3dea02b-oliver.sang@intel.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <202401251429.d3dea02b-oliver.sang@intel.com>

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