From: kernel test robot <oliver.sang@intel.com>
To: "Thomas Weißschuh" <thomas.weissschuh@linutronix.de>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Thomas Gleixner <tglx@linutronix.de>, <oliver.sang@intel.com>
Subject: [linus:master] [x86/vdso] e93d2521b2: kernel-selftests.mm.run_vmtests.sh.virtual_address_range.fail
Date: Fri, 27 Dec 2024 13:15:35 +0800 [thread overview]
Message-ID: <202412271148.2656e485-lkp@intel.com> (raw)
Hello,
kernel test robot noticed "kernel-selftests.mm.run_vmtests.sh.virtual_address_range.fail" on:
commit: e93d2521b27f0439872dfa4e4b92a9be6d73496f ("x86/vdso: Split virtual clock pages into dedicated mapping")
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
[test failed on linus/master 4bbf9020becbfd8fc2c3da790855b7042fad455b]
[test failed on linux-next/master 8155b4ef3466f0e289e8fcc9e6e62f3f4dceeac2]
in testcase: kernel-selftests
version: kernel-selftests-x86_64-7503345ac5f5-1_20241208
with following parameters:
group: mm
sc_nr_hugepages: 2
config: x86_64-rhel-9.4-kselftests
compiler: gcc-12
test machine: 36 threads 1 sockets Intel(R) Core(TM) i9-10980XE CPU @ 3.00GHz (Cascade Lake) with 32G 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/202412271148.2656e485-lkp@intel.com
# # -------------------------------
# # running ./virtual_address_range
# # -------------------------------
# # TAP version 13
# # 1..1
# # not ok 1 BUG in mmap() or /proc/self/maps
# # # Totals: pass:0 fail:1 xfail:0 xpass:0 skip:0 error:0
# # [FAIL]
# not ok 31 virtual_address_range # exit=1
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20241227/202412271148.2656e485-lkp@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-12-27 5:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202412271148.2656e485-lkp@intel.com \
--to=oliver.sang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=tglx@linutronix.de \
--cc=thomas.weissschuh@linutronix.de \
/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
all inboxes | Powered by JetHome®