From: kernel test robot <oliver.sang@intel.com>
To: Al Viro <viro@zeniv.linux.org.uk>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Matthew Wilcox <willy@infradead.org>, <linux-mm@kvack.org>,
<xudong.hao@intel.com>, <oliver.sang@intel.com>
Subject: [linux-next:master] [vmscan] a7694ff11a: kernel-selftests.kvm.access_tracking_perf_test.fail
Date: Wed, 16 Jul 2025 15:54:05 +0800 [thread overview]
Message-ID: <202507160818.49e37313-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.kvm.access_tracking_perf_test.fail" on:
commit: a7694ff11aa9d97d0f690351a964544849e5158d ("vmscan: don't bother with debugfs_real_fops()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 0be23810e32e6d0a17df7c0ebad895ba2c210fc4]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-7ff71e6d9239-1_20250215
with following parameters:
group: kvm
config: x86_64-rhel-9.4-kselftests
compiler: gcc-12
test machine: 64 threads 2 sockets Intel(R) Xeon(R) Gold 6346 CPU @ 3.10GHz (Ice Lake) with 256G memory
(please refer to attached dmesg/kmsg for entire log/backtrace)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <oliver.sang@intel.com>
| Closes: https://lore.kernel.org/oe-lkp/202507160818.49e37313-lkp@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20250716/202507160818.49e37313-lkp@intel.com
# timeout set to 120
# selftests: kvm: access_tracking_perf_test
# Random seed: 0x6b8b4567
# Skipping idle page count sanity check, because NUMA balancing is enabled
# Using lru_gen for aging
# Creating cgroup: /sys/fs/cgroup/access_tracking_perf_test
# Testing guest mode: PA-bits:ANY, VA-bits:48, 4K pages
# guest physical test memory: [0x3fffbffff000, 0x3ffffffff000)
#
# Populating memory : 2.190023000s
# Initial aging pass (lru_gen)
# ==== Test Assertion Failure ====
# lib/lru_gen_util.c:166: *end == '\0'
# pid=13434 tid=13434 errno=0 - Success
# 1 0x0000000000408dd8: memcg_stats_handle_in_node at lru_gen_util.c:166
# 2 0x0000000000409034: lru_gen_read_memcg_stats at lru_gen_util.c:221
# 3 0x00000000004091e0: lru_gen_do_aging at lru_gen_util.c:309
# 4 0x0000000000403526: run_test at access_tracking_perf_test.c:436
# 5 0x0000000000403d8c: for_each_guest_mode at guest_modes.c:96
# 6 0x0000000000402bfd: run_test_for_each_guest_mode at access_tracking_perf_test.c:486
# 7 0x000000000041d993: cg_run at cgroup_util.c:382
# 8 0x0000000000402869: main at access_tracking_perf_test.c:591
# 9 0x00007fed7a779249: ?? ??:0
# 10 0x00007fed7a779304: ?? ??:0
# 11 0x0000000000402990: _start at ??:?
# malformed generation age '0r'
not ok 76 selftests: kvm: access_tracking_perf_test # exit=254
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2025-07-16 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 7:54 kernel test robot [this message]
2025-07-16 10:22 ` 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=202507160818.49e37313-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.org \
--cc=xudong.hao@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