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
Date: Thu, 25 Jan 2024 12:01:56 +0000 [thread overview]
Message-ID: <ZbJNtFO_N4pVuEUK@arm.com> (raw)
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
next prev parent reply other threads:[~2024-01-25 12:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 7:34 kernel test robot
2024-01-25 12:01 ` Catalin Marinas [this message]
2024-01-26 6:35 ` Oliver Sang
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=ZbJNtFO_N4pVuEUK@arm.com \
--to=catalin.marinas@arm.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=longman@redhat.com \
--cc=oe-lkp@lists.linux.dev \
--cc=oliver.sang@intel.com \
/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