From: kernel test robot <lkp@intel.com>
To: Martin KaFai Lau <martin.lau@kernel.org>
Cc: oe-kbuild-all@lists.linux.dev, Martin KaFai Lau <martin.lau@linux.dev>
Subject: [martin-lau-bpf-next:cgrp.struct_ops.v8 9/12] kernel/bpf/cgroup.c:31:6: warning: conflicting types for 'bpf_cgroup_struct_ops_register' due to enum/integer mismatch; have 'void(enum cgroup_bpf_attach_type, u32, void *, bool)' {aka 'void(enum cgroup_bpf_attach_type, unsigned int, void *, _Bool)'}
Date: Sat, 16 May 2026 20:08:30 +0800 [thread overview]
Message-ID: <202605162022.KKnVwAAL-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/martin.lau/bpf-next.git cgrp.struct_ops.v8
head: 1ae5eccb04d5d8c62c310b206b5e5dc4ff1d9c71
commit: 32e27daf9a1563276f88eb17d076f61f8cc8b502 [9/12] bpf: Add infrastructure to support attaching struct_ops to cgroups
config: sh-allyesconfig (https://download.01.org/0day-ci/archive/20260516/202605162022.KKnVwAAL-lkp@intel.com/config)
compiler: sh4-linux-gcc (GCC) 15.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260516/202605162022.KKnVwAAL-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/202605162022.KKnVwAAL-lkp@intel.com/
All warnings (new ones prefixed by >>):
>> kernel/bpf/cgroup.c:31:6: warning: conflicting types for 'bpf_cgroup_struct_ops_register' due to enum/integer mismatch; have 'void(enum cgroup_bpf_attach_type, u32, void *, bool)' {aka 'void(enum cgroup_bpf_attach_type, unsigned int, void *, _Bool)'} [-Wenum-int-mismatch]
31 | void bpf_cgroup_struct_ops_register(enum cgroup_bpf_attach_type atype, u32 type_id,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from kernel/bpf/cgroup.c:16:
include/linux/bpf-cgroup.h:115:6: note: previous declaration of 'bpf_cgroup_struct_ops_register' with type 'void(int, u32, void *, bool)' {aka 'void(int, unsigned int, void *, _Bool)'}
115 | void bpf_cgroup_struct_ops_register(int atype, u32 type_id, void *cfi_stubs, bool tasks_trace);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
vim +31 kernel/bpf/cgroup.c
30
> 31 void bpf_cgroup_struct_ops_register(enum cgroup_bpf_attach_type atype, u32 type_id,
32 void *cfi_stubs, bool mult_rcu)
33 {
34 struct_ops_type_id[atype] = type_id;
35 struct_ops_cfi_stubs[atype] = cfi_stubs;
36 struct_ops_mult_rcu[atype] = mult_rcu;
37 }
38
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next reply other threads:[~2026-05-16 12:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-16 12:08 kernel test robot [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-05-16 10:36 [martin-lau-bpf-next:cgrp.struct_ops.v8 9/12] kernel/bpf/cgroup.c:31:6: warning: conflicting types for 'bpf_cgroup_struct_ops_register' due to enum/integer mismatch; have 'void(enum cgroup_bpf_attach_type, u32, void *, bool)' {aka 'void(enum cgroup_bpf_attach_type, unsigned int, void *, _Bool)'} kernel test robot
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=202605162022.KKnVwAAL-lkp@intel.com \
--to=lkp@intel.com \
--cc=martin.lau@kernel.org \
--cc=martin.lau@linux.dev \
--cc=oe-kbuild-all@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 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.