From: kernel test robot <oliver.sang@intel.com>
To: Kefeng Wang <wangkefeng.wang@huawei.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
Linux Memory Management List <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
"David Hildenbrand" <david@redhat.com>,
Miaohe Lin <linmiaohe@huawei.com>,
"Jonathan Cameron" <Jonathan.Cameron@huawei.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>,
Oscar Salvador <osalvador@suse.de>,
<linux-kernel@vger.kernel.org>, <ltp@lists.linux.it>,
<oliver.sang@intel.com>
Subject: [linux-next:master] [mm] f1295af16a: ltp.madvise11.fail
Date: Thu, 29 Aug 2024 16:13:15 +0800 [thread overview]
Message-ID: <202408291314.bdbfa468-oliver.sang@intel.com> (raw)
Hello,
kernel test robot noticed "ltp.madvise11.fail" on:
commit: f1295af16abee075de68400c58550cffacc29eb1 ("mm: migrate: add isolate_folio_to_list()")
https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git master
in testcase: ltp
version: ltp-x86_64-14c1f76-1_20240824
with following parameters:
disk: 1HDD
fs: btrfs
test: syscalls-01/madvise11
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/202408291314.bdbfa468-oliver.sang@intel.com
Running tests.......
<<<test_start>>>
tag=madvise11 stime=1724842748
cmdline="madvise11"
contacts=""
analysis=exit
<<<test_output>>>
tst_kconfig.c:88: TINFO: Parsing kernel config '/proc/config.gz'
tst_tmpdir.c:316: TINFO: Using /fs/sdb2/tmpdir/ltp-hqYc9wKboz/LTP_mad3BrMXR as tmpdir (btrfs filesystem)
tst_test.c:1809: TINFO: LTP version: 20240524-199-g2b319e3dc
tst_test.c:1813: TINFO: Tested kernel: 6.11.0-rc4-00294-gf1295af16abe #1 SMP PREEMPT_DYNAMIC Wed Aug 28 13:58:59 CST 2024 x86_64
tst_test.c:1652: TINFO: Timeout per run is 0h 03m 30s
madvise11.c:411: TINFO: Spawning 5 threads, with a total of 800 memory pages
madvise11.c:165: TINFO: Thread [0] returned 0, succeeded.
madvise11.c:165: TINFO: Thread [3] returned 0, succeeded.
madvise11.c:165: TINFO: Thread [1] returned 0, succeeded.
madvise11.c:165: TINFO: Thread [4] returned 0, succeeded.
madvise11.c:165: TINFO: Thread [2] returned 0, succeeded.
madvise11.c:200: TPASS: soft-offline / mmap race still clean
madvise11.c:363: TINFO: Restore 800 Soft-offlined pages
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
< a lot of same output here >
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
madvise11.c:292: TWARN: write(4,0x7ffe64ed2d80,8) failed: EBUSY (16)
Summary:
passed 1
failed 0
broken 0
skipped 0
warnings 800
incrementing stop
<<<execution_status>>>
initiation_status="ok"
duration=20 termination_type=exited termination_id=4 corefile=no
cutime=1 cstime=3724
<<<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/20240829/202408291314.bdbfa468-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2024-08-29 8:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 8:13 kernel test robot [this message]
2024-08-29 8:20 ` Kefeng Wang
2024-08-30 8:21 ` 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=202408291314.bdbfa468-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=ltp@lists.linux.it \
--cc=nao.horiguchi@gmail.com \
--cc=oe-lkp@lists.linux.dev \
--cc=osalvador@suse.de \
--cc=wangkefeng.wang@huawei.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