From: Oliver Sang <oliver.sang@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: <oe-lkp@lists.linux.dev>, <lkp@intel.com>,
<linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jonathan Corbet <corbet@lwn.net>, <damon@lists.linux.dev>,
<linux-mm@kvack.org>
Subject: Re: [linus:master] [mm/damon/sysfs] 9a5aa3349b: kernel-selftests.damon.damos_quota_goal.py.fail
Date: Tue, 18 Feb 2025 10:53:12 +0800 [thread overview]
Message-ID: <Z7P2GBp9JWLfn2zH@xsang-OptiPlex-9020> (raw)
In-Reply-To: <20250217182435.45244-1-sj@kernel.org>
hi, SJ,
On Mon, Feb 17, 2025 at 10:24:35AM -0800, SeongJae Park wrote:
> Hello,
>
> On Mon, 17 Feb 2025 15:01:23 +0800 kernel test robot <oliver.sang@intel.com> wrote:
>
> >
> >
> > Hello,
> >
> > kernel test robot noticed "kernel-selftests.damon.damos_quota_goal.py.fail" on:
> >
> > commit: 9a5aa3349b9428ae451b22c331d0d9a9cfc7ac90 ("mm/damon/sysfs: use damon_call() for update_schemes_effective_quotas")
> > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git master
> >
> > [test failed on linus/master 0ad2507d5d93f39619fc42372c347d6006b64319]
> > [test failed on linux-next/master 0ae0fa3bf0b44c8611d114a9f69985bf451010c3]
> >
> > in testcase: kernel-selftests
> > version: kernel-selftests-x86_64-7ff71e6d9239-1_20250215
> > with following parameters:
> >
> > group: damon
> >
> >
> >
> > config: x86_64-dcg_x86_64_defconfig-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/202502171423.b28a918d-lkp@intel.com
> >
> >
> >
> > # timeout set to 300
> > # selftests: damon: damos_quota_goal.py
> > # score: 0, effective quota: 0 -> 16 (-1.000x)
> > # score: 15000, effective quota: 16 -> 1 (0.062x)
> > # score: 5000, effective quota: 1 -> 5 (5.000x)
> > # score: 18000, effective quota: 1 -> 1 (1.000x)
> > # efective bytes not changed: 1
> > not ok 7 selftests: damon: damos_quota_goal.py # exit=1
>
> Thank you for this report! I just posted a fix[1] for this case. Please refer
> to the patch for details including the root cause.
thanks a lot for information!
>
> [1] https://lore.kernel.org/20250217182304.45215-1-sj@kernel.org
>
>
> Thanks,
> SJ
>
> >
> >
> >
> > The kernel config and materials to reproduce are available at:
> > https://download.01.org/0day-ci/archive/20250217/202502171423.b28a918d-lkp@intel.com
> >
> >
> >
> > --
> > 0-DAY CI Kernel Test Service
> > https://github.com/intel/lkp-tests/wiki
>
prev parent reply other threads:[~2025-02-18 2:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 7:01 kernel test robot
2025-02-17 18:24 ` SeongJae Park
2025-02-18 2:53 ` Oliver Sang [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=Z7P2GBp9JWLfn2zH@xsang-OptiPlex-9020 \
--to=oliver.sang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--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 \
/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