From: Mark Brown <broonie@kernel•org>
To: Tejun Heo <tj@kernel•org>
Cc: Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>
Subject: linux-next: build failure after merge of the sched-ext tree
Date: Tue, 26 May 2026 14:51:41 +0100 [thread overview]
Message-ID: <ahWlbaHoXGo5icZj@sirena.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1037 bytes --]
Hi all,
After merging the sched-ext tree, today's linux-next build (arm_multi_v7
defconfig) failed like this:
/tmp/next/build/kernel/bpf/core.c:3379:13: error: redefinition of
'bpf_arena_handle_page_fault'
3379 | __weak bool bpf_arena_handle_page_fault(unsigned long addr, bool is_write,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /tmp/next/build/include/linux/bpf.h:9,
from /tmp/next/build/include/linux/filter.h:9,
from /tmp/next/build/kernel/bpf/core.c:21:
/tmp/next/build/include/linux/bpf_defs.h:12:20: note: previous definition
of 'bpf_arena_handle_page_fault' with type 'bool(long unsigned int,
bool, long unsigned int)' {aka '_Bool(long unsigned int, _Bool, long
unsigned int)'}
12 | static inline bool bpf_arena_handle_page_fault(unsigned long addr, bool is_write,
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
Caused by commit
dc11a4dba2464 (bpf: Recover arena kernel faults with scratch page)
I have used the version from next-20260525 instead.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2026-05-26 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-26 13:51 Mark Brown [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-10-22 11:29 linux-next: build failure after merge of the sched-ext tree Stephen Rothwell
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=ahWlbaHoXGo5icZj@sirena.org.uk \
--to=broonie@kernel$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=tj@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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