From: kernel test robot <oliver.sang@intel.com>
To: Alex Rusuf <yorha.op@gmail.com>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<damon@lists.linux.dev>, <linux-mm@kvack.org>, <sj@kernel.org>,
<linux-kernel@vger.kernel.org>, <oliver.sang@intel.com>
Subject: Re: [PATCH v2 2/2] mm/damon/core: implement multi-context support
Date: Mon, 17 Jun 2024 14:59:16 +0800 [thread overview]
Message-ID: <202406171435.2c3aa362-oliver.sang@intel.com> (raw)
In-Reply-To: <20240531122320.909060-3-yorha.op@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1603 bytes --]
Hello,
kernel test robot noticed "kernel-selftests.damon.sysfs.sh.fail" on:
commit: c1c2595bf89a145e63d08dbfa297951caaa91544 ("[PATCH v2 2/2] mm/damon/core: implement multi-context support")
url: https://github.com/intel-lab-lkp/linux/commits/Alex-Rusuf/mm-damon-core-add-struct-kdamond-abstraction-layer/20240531-202756
base: v6.9
patch link: https://lore.kernel.org/all/20240531122320.909060-3-yorha.op@gmail.com/
patch subject: [PATCH v2 2/2] mm/damon/core: implement multi-context support
in testcase: kernel-selftests
version: kernel-selftests-x86_64-977d51cf-1_20240508
with following parameters:
group: group-01
compiler: gcc-13
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/202406171435.2c3aa362-oliver.sang@intel.com
The kernel config and materials to reproduce are available at:
https://download.01.org/0day-ci/archive/20240617/202406171435.2c3aa362-oliver.sang@intel.com
(as in attached kernel-selftests.xz)
# timeout set to 300
# selftests: damon: sysfs.sh
# writing 2 to /sys/kernel/mm/damon/admin/kdamonds/0/contexts/nr_contexts succeed ()
# expected failure because only 0/1 are supported
not ok 10 selftests: damon: sysfs.sh # exit=1
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
[-- Attachment #2: kernel-selftests.xz --]
[-- Type: application/x-xz, Size: 29824 bytes --]
next prev parent reply other threads:[~2024-06-17 6:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 12:23 [PATCH v2 0/2] DAMON multiple contexts support Alex Rusuf
2024-05-31 12:23 ` [PATCH v2 1/2] mm/damon/core: add 'struct kdamond' abstraction layer Alex Rusuf
2024-05-31 18:55 ` kernel test robot
2024-05-31 19:36 ` SeongJae Park
2024-06-02 16:15 ` Alex Rusuf
2024-06-02 16:51 ` SeongJae Park
2024-05-31 12:23 ` [PATCH v2 2/2] mm/damon/core: implement multi-context support Alex Rusuf
2024-05-31 19:26 ` kernel test robot
2024-05-31 19:38 ` SeongJae Park
2024-06-02 15:08 ` Alex Rusuf
2024-06-02 15:48 ` SeongJae Park
2024-06-02 19:48 ` Alex Rusuf
2024-06-03 18:45 ` SeongJae Park
2024-05-31 20:08 ` kernel test robot
2024-06-17 6:59 ` kernel test robot [this message]
2024-05-31 19:33 ` [PATCH v2 0/2] DAMON multiple contexts support SeongJae Park
2024-06-02 15:31 ` Alex Rusuf
2024-06-02 15:56 ` SeongJae Park
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=202406171435.2c3aa362-oliver.sang@intel.com \
--to=oliver.sang@intel.com \
--cc=damon@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=sj@kernel.org \
--cc=yorha.op@gmail.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