From: kernel test robot <lkp@intel.com>
To: SeongJae Park <sj@kernel.org>
Cc: llvm@lists.linux.dev, kbuild-all@lists.01.org
Subject: Re: [PATCH] mm/damon/sysfs: fix pid leak under fvaddr ops use case
Date: Wed, 4 May 2022 10:53:47 +0800 [thread overview]
Message-ID: <202205041011.jv6vuDe4-lkp@intel.com> (raw)
In-Reply-To: <20220503220531.45913-1-sj@kernel.org>
Hi SeongJae,
I love your patch! Yet something to improve:
[auto build test ERROR on hnaz-mm/master]
url: https://github.com/intel-lab-lkp/linux/commits/SeongJae-Park/mm-damon-sysfs-fix-pid-leak-under-fvaddr-ops-use-case/20220504-060657
base: https://github.com/hnaz/linux-mm master
config: hexagon-randconfig-r045-20220501 (https://download.01.org/0day-ci/archive/20220504/202205041011.jv6vuDe4-lkp@intel.com/config)
compiler: clang version 15.0.0 (https://github.com/llvm/llvm-project 363b3a645a1e30011cc8da624f13dac5fd915628)
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/intel-lab-lkp/linux/commit/60cfe4571b04ef4ca2e34793fbad737bb43dc0c6
git remote add linux-review https://github.com/intel-lab-lkp/linux
git fetch --no-tags linux-review SeongJae-Park/mm-damon-sysfs-fix-pid-leak-under-fvaddr-ops-use-case/20220504-060657
git checkout 60cfe4571b04ef4ca2e34793fbad737bb43dc0c6
# save the config file
mkdir build_dir && cp config build_dir/.config
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=clang make.cross W=1 O=build_dir ARCH=hexagon SHELL=/bin/bash mm/damon/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
>> mm/damon/sysfs.c:2089:20: error: use of undeclared identifier 'DAMON_OPS_FVADDR'; did you mean 'DAMON_OPS_VADDR'?
ctx->ops.id == DAMON_OPS_FVADDR)
^~~~~~~~~~~~~~~~
DAMON_OPS_VADDR
include/linux/damon.h:267:2: note: 'DAMON_OPS_VADDR' declared here
DAMON_OPS_VADDR,
^
mm/damon/sysfs.c:2206:55: error: use of undeclared identifier 'DAMON_OPS_FVADDR'; did you mean 'DAMON_OPS_VADDR'?
if (ctx->ops.id != DAMON_OPS_VADDR && ctx->ops.id != DAMON_OPS_FVADDR)
^~~~~~~~~~~~~~~~
DAMON_OPS_VADDR
include/linux/damon.h:267:2: note: 'DAMON_OPS_VADDR' declared here
DAMON_OPS_VADDR,
^
2 errors generated.
vim +2089 mm/damon/sysfs.c
2082
2083 static void damon_sysfs_destroy_targets(struct damon_ctx *ctx)
2084 {
2085 struct damon_target *t, *next;
2086
2087 damon_for_each_target_safe(t, next, ctx) {
2088 if (ctx->ops.id == DAMON_OPS_VADDR ||
> 2089 ctx->ops.id == DAMON_OPS_FVADDR)
2090 put_pid(t->pid);
2091 damon_destroy_target(t);
2092 }
2093 }
2094
--
0-DAY CI Kernel Test Service
https://01.org/lkp
next parent reply other threads:[~2022-05-04 2:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220503220531.45913-1-sj@kernel.org>
2022-05-04 2:53 ` kernel test robot [this message]
2022-05-04 17:16 ` [PATCH] mm/damon/sysfs: fix pid leak under fvaddr ops use case SeongJae Park
2022-05-06 8:19 ` [kbuild-all] " Chen, Rong A
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=202205041011.jv6vuDe4-lkp@intel.com \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.org \
--cc=llvm@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;
as well as URLs for NNTP newsgroup(s).