From: kernel test robot <oliver.sang@intel.com>
To: Wei Yang <richard.weiyang@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>, <linux-mm@kvack.org>,
<rppt@kernel.org>, <akpm@linux-foundation.org>,
<david@redhat.com>, <osalvador@suse.de>,
Wei Yang <richard.weiyang@gmail.com>, <oliver.sang@intel.com>
Subject: Re: [PATCH] mm: increase totalram_pages on freeing to buddy system
Date: Tue, 11 Jun 2024 16:48:28 +0800 [thread overview]
Message-ID: <202406111644.931d379c-oliver.sang@intel.com> (raw)
In-Reply-To: <20240601133402.2675-1-richard.weiyang@gmail.com>
Hello,
kernel test robot noticed "xfstests.generic.224.fail" on:
commit: a4722639595dc3fa15c793a5b00bb4b023a34288 ("[PATCH] mm: increase totalram_pages on freeing to buddy system")
url: https://github.com/intel-lab-lkp/linux/commits/Wei-Yang/mm-increase-totalram_pages-on-freeing-to-buddy-system/20240601-213533
base: https://git.kernel.org/cgit/linux/kernel/git/akpm/mm.git mm-everything
patch link: https://lore.kernel.org/all/20240601133402.2675-1-richard.weiyang@gmail.com/
patch subject: [PATCH] mm: increase totalram_pages on freeing to buddy system
in testcase: xfstests
version: xfstests-x86_64-98379713-1_20240603
with following parameters:
disk: 4HDD
fs: udf
test: generic-224
compiler: gcc-13
test machine: 4 threads Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz (Skylake) 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/202406111644.931d379c-oliver.sang@intel.com
2024-06-09 06:39:08 export TEST_DIR=/fs/sda1
2024-06-09 06:39:08 export TEST_DEV=/dev/sda1
2024-06-09 06:39:08 export FSTYP=udf
2024-06-09 06:39:08 export SCRATCH_MNT=/fs/scratch
2024-06-09 06:39:08 mkdir /fs/scratch -p
2024-06-09 06:39:08 export DISABLE_UDF_TEST=1
2024-06-09 06:39:08 export SCRATCH_DEV=/dev/sda4
2024-06-09 06:39:08 echo generic/224
2024-06-09 06:39:08 ./check generic/224
FSTYP -- udf
PLATFORM -- Linux/x86_64 lkp-skl-d02 6.10.0-rc1-00201-ga4722639595d #1 SMP PREEMPT_DYNAMIC Fri Jun 7 19:31:50 CST 2024
MKFS_OPTIONS -- /dev/sda4
MOUNT_OPTIONS -- /dev/sda4 /fs/scratch
generic/224 [failed, exit status 1]- output mismatch (see /lkp/benchmarks/xfstests/results//generic/224.out.bad)
--- tests/generic/224.out 2024-06-03 12:10:00.000000000 +0000
+++ /lkp/benchmarks/xfstests/results//generic/224.out.bad 2024-06-09 06:41:46.383320015 +0000
@@ -1,2 +1,34 @@
QA output created by 224
-*** Silence is golden ***
+/lkp/benchmarks/xfstests/tests/generic/224: fork: retry: Resource temporarily unavailable
+/lkp/benchmarks/xfstests/tests/generic/224: fork: retry: Resource temporarily unavailable
+/lkp/benchmarks/xfstests/tests/generic/224: fork: retry: Resource temporarily unavailable
+/lkp/benchmarks/xfstests/tests/generic/224: fork: retry: Resource temporarily unavailable
+/lkp/benchmarks/xfstests/tests/generic/224: fork: retry: Resource temporarily unavailable
...
(Run 'diff -u /lkp/benchmarks/xfstests/tests/generic/224.out /lkp/benchmarks/xfstests/results//generic/224.out.bad' to see the entire diff)
Ran: generic/224
Failures: generic/224
Failed 1 of 1 tests
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240611/202406111644.931d379c-oliver.sang@intel.com
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-06-11 8:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-01 13:34 Wei Yang
[not found] ` <0316a276-a0d8-4fc2-ad67-0d4732b6d89b@redhat.com>
[not found] ` <ac1a80a8-1a4f-47b6-8fc4-ce220ba76ead@redhat.com>
2024-06-02 0:58 ` Wei Yang
2024-06-03 8:55 ` David Hildenbrand
2024-06-03 20:01 ` Wei Yang
2024-06-03 20:43 ` David Hildenbrand
2024-06-05 22:44 ` Wei Yang
2024-06-06 7:14 ` David Hildenbrand
2024-06-06 23:25 ` Wei Yang
2024-06-07 1:50 ` Wei Yang
2024-06-11 8:48 ` kernel test robot [this message]
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=202406111644.931d379c-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=osalvador@suse.de \
--cc=richard.weiyang@gmail.com \
--cc=rppt@kernel.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