DAMON development mailing list
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: kernel test robot <lkp@intel.com>
Cc: SeongJae Park <sj@kernel.org>,
	oe-kbuild@lists.linux.dev, damon@lists.linux.dev
Subject: Re: [sj:damon/next 145/145] mm/memory.c:6213:9: error: implicit declaration of function 'damon_report_page_fault'
Date: Mon,  1 Dec 2025 17:06:48 -0800	[thread overview]
Message-ID: <20251202010649.71271-1-sj@kernel.org> (raw)
In-Reply-To: <202512011308.JsZqQIqQ-lkp@intel.com>

On Mon, 1 Dec 2025 13:19:13 +0800 kernel test robot <lkp@intel.com> wrote:

> :::::: 
> :::::: Manual check reason: "low confidence bisect report"
> :::::: 
> 
> BCC: lkp@intel.com
> CC: oe-kbuild-all@lists.linux.dev
> TO: SeongJae Park <sj@kernel.org>
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/sj/linux.git damon/next
> head:   3fdd82439d28bd0bc5eeb347a6e96569ae05ec92
> commit: 3fdd82439d28bd0bc5eeb347a6e96569ae05ec92 [145/145] mm/memory: move fault reporting into damon
> :::::: branch date: 7 hours ago
> :::::: commit date: 7 hours ago
> config: riscv-allnoconfig-bpf (https://download.01.org/0day-ci/archive/20251201/202512011308.JsZqQIqQ-lkp@intel.com/config)
> compiler: riscv64-linux-gcc (GCC) 15.1.0
> reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251201/202512011308.JsZqQIqQ-lkp@intel.com/reproduce)
> 
> 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 <lkp@intel.com>
> | Closes: https://lore.kernel.org/r/202512011308.JsZqQIqQ-lkp@intel.com/
> 
> All errors (new ones prefixed by >>):
> 
>    mm/memory.c: In function 'do_damon_page':
> >> mm/memory.c:6213:9: error: implicit declaration of function 'damon_report_page_fault' [-Wimplicit-function-declaration]
>     6213 |         damon_report_page_fault(vmf, huge_pmd);
>          |         ^~~~~~~~~~~~~~~~~~~~~~~

Thank you for this report!  Seems this happens when COFNIG_DAMON is unset.  I
just pushed a fix:
http://git.kernel.org/sj/c/47b20fdc07850bd8f


Thanks,
SJ

[...]

           reply	other threads:[~2025-12-02  1:06 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <202512011308.JsZqQIqQ-lkp@intel.com>]

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=20251202010649.71271-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=lkp@intel.com \
    --cc=oe-kbuild@lists.linux.dev \
    /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