From: kernel test robot <lkp@intel.com>
To: jason.zeng@intel.com, lin.x.wang@intel.com, pei.p.jia@intel.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [bytedance:5.15-velinux 0/350] mm/oom_kill.c:318:14: warning: no previous prototype for 'bpf_oom_evaluate_task'
Date: Fri, 9 May 2025 02:26:33 +0800 [thread overview]
Message-ID: <202505090238.fChHRDLp-lkp@intel.com> (raw)
Hi Chuyi,
FYI, the error/warning still remains.
tree: https://github.com/bytedance/kernel.git 5.15-velinux
head: de277dab626c9ece4c9cf99ec9c56f23b298a042
commit: 9cffac2e6f2df386d7cf4c2cf90d5fe2c1d6b793 [0/350] bytedance: mm, oom: Introduce bpf_oom_evaluate_task
config: arm64-allnoconfig (https://download.01.org/0day-ci/archive/20250509/202505090238.fChHRDLp-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250509/202505090238.fChHRDLp-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/oe-kbuild-all/202505090238.fChHRDLp-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> mm/oom_kill.c:318:14: warning: no previous prototype for 'bpf_oom_evaluate_task' [-Wmissing-prototypes]
318 | noinline int bpf_oom_evaluate_task(struct task_struct *task, struct oom_control *oc)
| ^~~~~~~~~~~~~~~~~~~~~
vim +/bpf_oom_evaluate_task +318 mm/oom_kill.c
317
> 318 noinline int bpf_oom_evaluate_task(struct task_struct *task, struct oom_control *oc)
319 {
320 return NO_BPF_POLICY;
321 }
322 ALLOW_ERROR_INJECTION(bpf_oom_evaluate_task, ERRNO);
323
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-05-08 18:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=202505090238.fChHRDLp-lkp@intel.com \
--to=lkp@intel.com \
--cc=jason.zeng@intel.com \
--cc=lin.x.wang@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pei.p.jia@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.