From: kernel test robot <oliver.sang@intel.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Lorenzo Stoakes" <lorenzo.stoakes@oracle.com>,
Bert Karwatzki <spasswolf@web.de>, Jiri Olsa <olsajiri@gmail.com>,
Kees Cook <kees@kernel.org>,
"Lorenzo Stoakes" <lstoakes@gmail.com>,
Matthew Wilcox <willy@infradead.org>,
"Paul E. McKenney" <paulmck@kernel.org>,
Paul Moore <paul@paul-moore.com>,
"Sidhartha Kumar" <sidhartha.kumar@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Vlastimil Babka <vbabka@suse.cz>, <ltp@lists.linux.it>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [mm/vma] c2eb22189b: ltp.mseal01.fail
Date: Sat, 31 Aug 2024 21:52:44 +0800 [thread overview]
Message-ID: <202408312155.fd26a58c-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.mseal01.fail" on:
commit: c2eb22189bbc920cdc667dfaf939878031194bb6 ("mm/vma: inline munmap operation in mmap_region()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
[test failed on linux-next/master 985bf40edf4343dcb04c33f58b40b4a85c1776d4]
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20240824
with following parameters:
disk: 1HDD
fs: btrfs
test: syscalls-02/mseal01
compiler: gcc-12
test machine: 4 threads 1 sockets Intel(R) Core(TM) i3-3220 CPU @ 3.30GHz (Ivy Bridge) with 8G 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/202408312155.fd26a58c-oliver.sang@intel.com
Running tests.......
<<<test_start>>>
tag=mseal01 stime=1725009411
cmdline="mseal01"
contacts=""
analysis=exit
<<<test_output>>>
tst_test.c:1809: TINFO: LTP version: 20240524-199-g2b319e3dc
tst_test.c:1813: TINFO: Tested kernel: 6.11.0-rc4-00355-gc2eb22189bbc #1 SMP PREEMPT_DYNAMIC Thu Aug 29 21:27:00 CST 2024 x86_64
tst_test.c:1652: TINFO: Timeout per run is 0h 02m 30s
mseal01.c:132: TINFO: Testing mprotect() availability
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
mseal01.c:47: TPASS: mprotect(mem_addr, mem_size, PROT_NONE) : EPERM (1)
mseal01.c:132: TINFO: Testing pkey_mprotect() availability
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
../../../../include/lapi/pkey.h:49: TCONF: pku is not supported on this CPU
mseal01.c:132: TINFO: Testing madvise() availability
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
mseal01.c:72: TPASS: madvise(mem_addr, mem_size, MADV_DONTNEED) : EPERM (1)
mseal01.c:132: TINFO: Testing munmap() availability from child
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
mseal01.c:77: TPASS: munmap(mem_addr, mem_size) : EPERM (1)
mseal01.c:132: TINFO: Testing mremap() address move/resize
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
mseal01.c:90: TPASS: mremap(mem_addr, mem_size, new_size, MREMAP_MAYMOVE | MREMAP_FIXED, new_addr) : EPERM (1)
mseal01.c:132: TINFO: Testing mmap() protection change
mseal01.c:134: TPASS: sys_mseal(mem_addr + mem_offset, mem_alignment) passed
mseal01.c:100: TFAIL: mmap(mem_addr, mem_size, PROT_READ, MAP_ANONYMOUS | MAP_PRIVATE | MAP_FIXED, -1, 0) expected EPERM: ENOMEM (12)
Summary:
passed 10
failed 1
broken 0
skipped 1
warnings 0
incrementing stop
<<<execution_status>>>
initiation_status="ok"
duration=0 termination_type=exited termination_id=1 corefile=no
cutime=0 cstime=2
<<<test_end>>>
INFO: ltp-pan reported some tests FAIL
LTP Version: 20240524-199-g2b319e3dc
###############################################################
Done executing testcases.
LTP Version: 20240524-199-g2b319e3dc
###############################################################
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240831/202408312155.fd26a58c-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-08-31 13:53 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=202408312155.fd26a58c-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kees@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=lstoakes@gmail.com \
--cc=ltp@lists.linux.it \
--cc=oe-lkp@lists.linux.dev \
--cc=olsajiri@gmail.com \
--cc=paul@paul-moore.com \
--cc=paulmck@kernel.org \
--cc=sidhartha.kumar@oracle.com \
--cc=spasswolf@web.de \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
/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