From: kernel test robot <lkp@intel.com>
To: Ben Hutchings <bwh@kernel.org>, bpf@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev, Ben Hutchings <bwh@kernel.org>,
Dinh Nguyen <dinguyen@kernel.org>,
linux-openrisc@vger.kernel.org, Chris Zankel <chris@zankel.net>,
Max Filippov <jcmvbkbc@gmail.com>
Subject: Re: [PATCH] nios2, openrisc, xtensa: Fix definitions of bpf_user_pt_regs_t
Date: Sun, 24 Aug 2025 07:16:22 +0800 [thread overview]
Message-ID: <202508240726.GADEDNYH-lkp@intel.com> (raw)
In-Reply-To: <20250822135848.1922288-1-ben.hutchings@mind.be>
Hi Ben,
kernel test robot noticed the following build errors:
[auto build test ERROR on linus/master]
[also build test ERROR on openrisc/for-next jcmvbkbc-xtensa/xtensa-for-next v6.17-rc2 next-20250822]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Ben-Hutchings/nios2-openrisc-xtensa-Fix-definitions-of-bpf_user_pt_regs_t/20250822-220742
base: linus/master
patch link: https://lore.kernel.org/r/20250822135848.1922288-1-ben.hutchings%40mind.be
patch subject: [PATCH] nios2, openrisc, xtensa: Fix definitions of bpf_user_pt_regs_t
config: xtensa-allyesconfig (https://download.01.org/0day-ci/archive/20250824/202508240726.GADEDNYH-lkp@intel.com/config)
compiler: xtensa-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20250824/202508240726.GADEDNYH-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/202508240726.GADEDNYH-lkp@intel.com/
All errors (new ones prefixed by >>):
kernel/events/core.c: In function 'bpf_overflow_handler':
>> kernel/events/core.c:10208:18: error: assignment to 'bpf_user_pt_regs_t *' {aka 'struct user_pt_regs *'} from incompatible pointer type 'struct pt_regs *' [-Wincompatible-pointer-types]
10208 | ctx.regs = perf_arch_bpf_user_pt_regs(regs);
| ^
vim +10208 kernel/events/core.c
030a976efae83f Peter Zijlstra 2022-11-19 10195
4c03fe11b96bda Kyle Huey 2024-04-11 10196 #ifdef CONFIG_BPF_SYSCALL
f11f10bfa1ca23 Kyle Huey 2024-04-11 10197 static int bpf_overflow_handler(struct perf_event *event,
4c03fe11b96bda Kyle Huey 2024-04-11 10198 struct perf_sample_data *data,
4c03fe11b96bda Kyle Huey 2024-04-11 10199 struct pt_regs *regs)
4c03fe11b96bda Kyle Huey 2024-04-11 10200 {
4c03fe11b96bda Kyle Huey 2024-04-11 10201 struct bpf_perf_event_data_kern ctx = {
4c03fe11b96bda Kyle Huey 2024-04-11 10202 .data = data,
4c03fe11b96bda Kyle Huey 2024-04-11 10203 .event = event,
4c03fe11b96bda Kyle Huey 2024-04-11 10204 };
4c03fe11b96bda Kyle Huey 2024-04-11 10205 struct bpf_prog *prog;
4c03fe11b96bda Kyle Huey 2024-04-11 10206 int ret = 0;
4c03fe11b96bda Kyle Huey 2024-04-11 10207
4c03fe11b96bda Kyle Huey 2024-04-11 @10208 ctx.regs = perf_arch_bpf_user_pt_regs(regs);
4c03fe11b96bda Kyle Huey 2024-04-11 10209 if (unlikely(__this_cpu_inc_return(bpf_prog_active) != 1))
4c03fe11b96bda Kyle Huey 2024-04-11 10210 goto out;
4c03fe11b96bda Kyle Huey 2024-04-11 10211 rcu_read_lock();
4c03fe11b96bda Kyle Huey 2024-04-11 10212 prog = READ_ONCE(event->prog);
4c03fe11b96bda Kyle Huey 2024-04-11 10213 if (prog) {
4c03fe11b96bda Kyle Huey 2024-04-11 10214 perf_prepare_sample(data, event, regs);
4c03fe11b96bda Kyle Huey 2024-04-11 10215 ret = bpf_prog_run(prog, &ctx);
4c03fe11b96bda Kyle Huey 2024-04-11 10216 }
4c03fe11b96bda Kyle Huey 2024-04-11 10217 rcu_read_unlock();
4c03fe11b96bda Kyle Huey 2024-04-11 10218 out:
4c03fe11b96bda Kyle Huey 2024-04-11 10219 __this_cpu_dec(bpf_prog_active);
4c03fe11b96bda Kyle Huey 2024-04-11 10220
f11f10bfa1ca23 Kyle Huey 2024-04-11 10221 return ret;
4c03fe11b96bda Kyle Huey 2024-04-11 10222 }
4c03fe11b96bda Kyle Huey 2024-04-11 10223
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2025-08-23 23:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-22 13:58 [PATCH] nios2, openrisc, xtensa: Fix definitions of bpf_user_pt_regs_t Ben Hutchings
2025-08-23 5:45 ` Stafford Horne
2025-08-23 23:16 ` kernel test robot [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=202508240726.GADEDNYH-lkp@intel.com \
--to=lkp@intel.com \
--cc=bpf@vger.kernel.org \
--cc=bwh@kernel.org \
--cc=chris@zankel.net \
--cc=dinguyen@kernel.org \
--cc=jcmvbkbc@gmail.com \
--cc=linux-openrisc@vger.kernel.org \
--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.