From: Uros Bizjak <ubizjak@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Daniel Borkmann <daniel@iogearbox.net>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: build failure after merge of the bpf-next tree
Date: Wed, 19 Mar 2025 06:03:58 +0100 [thread overview]
Message-ID: <CAFULd4aaOPYMpSWN=FNueoqXDKKfLu7P0NLr2DU1J2HKgxr_8A@mail.gmail.com> (raw)
In-Reply-To: <20250319133309.6fce6404@canb.auug.org.au>
On Wed, Mar 19, 2025 at 3:33 AM Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Caused by the resilient-queued-spin-lock branch of the bpf-next tree
> interacting with the "Enable strict percpu address space checks" series
> form the mm-stable tree.
>
> I don't know why this happens, but reverting that branch inf the bpf-next
> tree makes the failure go away, so I have done that for today.
percpu pointers are now checked by the compiler, and their address
spaces have to be handled properly. It is like "sparse" rule, but now
enforced by the compiler.
This functionality was in fact introduced to catch programming errors like this.
Thanks,
Uros.
next prev parent reply other threads:[~2025-03-19 5:04 UTC|newest]
Thread overview: 103+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 2:33 linux-next: build failure after merge of the bpf-next tree Stephen Rothwell
2025-03-19 2:46 ` Alexei Starovoitov
2025-03-19 3:28 ` Stephen Rothwell
2025-03-19 13:37 ` Kumar Kartikeya Dwivedi
2025-03-19 13:43 ` Kumar Kartikeya Dwivedi
2025-03-19 14:36 ` Kumar Kartikeya Dwivedi
2025-03-19 14:55 ` Alexei Starovoitov
2025-03-19 15:11 ` Alexei Starovoitov
2025-03-19 16:06 ` Uros Bizjak
2025-03-19 18:56 ` Alexei Starovoitov
2025-03-19 19:43 ` Uros Bizjak
2025-03-19 23:16 ` Alexei Starovoitov
2025-03-20 7:49 ` Uros Bizjak
2025-03-20 23:17 ` Alexei Starovoitov
2025-03-21 7:15 ` Uros Bizjak
2025-03-19 5:03 ` Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-12 3:52 Stephen Rothwell
2024-10-16 6:05 Stephen Rothwell
2024-10-16 16:25 ` Alexei Starovoitov
2024-10-16 18:35 ` Namhyung Kim
2024-10-16 19:32 ` Alexei Starovoitov
2024-09-13 3:55 Stephen Rothwell
2024-09-13 4:00 ` Al Viro
2024-09-13 4:26 ` Andrii Nakryiko
2024-09-13 4:43 ` Al Viro
2024-09-15 23:30 ` Stephen Rothwell
2024-09-13 3:45 Stephen Rothwell
2024-09-13 3:48 ` Stephen Rothwell
2024-09-15 23:27 ` Stephen Rothwell
2024-09-13 3:32 Stephen Rothwell
2024-09-15 23:26 ` Stephen Rothwell
2024-08-14 1:25 Stephen Rothwell
2024-08-14 1:41 ` Al Viro
2024-08-14 2:37 ` Stephen Rothwell
2024-08-14 14:50 ` Christian Brauner
2024-08-30 1:32 ` Stephen Rothwell
2024-08-14 1:18 Stephen Rothwell
2024-06-17 18:15 Mark Brown
2024-06-22 8:17 ` kernel test robot
2024-06-22 8:28 ` kernel test robot
2024-06-25 1:22 ` Thinker Li
2024-06-25 15:54 ` Benjamin Tissoires
2024-06-25 16:03 ` Mark Brown
2024-06-25 17:14 ` Alexei Starovoitov
2024-06-27 7:14 ` Benjamin Tissoires
2024-07-09 23:13 ` Stephen Rothwell
2024-07-18 1:49 ` Stephen Rothwell
2024-07-18 7:42 ` Benjamin Tissoires
2023-03-19 23:26 Stephen Rothwell
2023-03-20 12:07 ` Alexander Lobakin
2023-03-21 22:35 ` Stephen Rothwell
2022-07-20 1:59 Stephen Rothwell
2022-07-20 3:42 ` Alexei Starovoitov
2022-07-20 3:44 ` Stanislav Fomichev
2022-04-19 1:56 Stephen Rothwell
2022-04-21 0:32 ` Stephen Rothwell
2022-04-21 9:45 ` Daniel Borkmann
2022-04-21 10:40 ` Maciej Fijalkowski
2022-02-09 0:21 Stephen Rothwell
2021-12-03 0:15 Stephen Rothwell
2021-09-14 1:37 Stephen Rothwell
2021-09-14 23:25 ` Andrii Nakryiko
2021-09-14 23:38 ` Stephen Rothwell
2021-09-14 23:40 ` Andrii Nakryiko
2021-09-14 23:59 ` Stephen Rothwell
2021-09-15 1:27 ` Alexei Starovoitov
2021-08-26 1:50 Stephen Rothwell
2021-08-26 2:01 ` Daniel Xu
2021-03-11 0:47 Stephen Rothwell
2021-03-11 6:47 ` Björn Töpel
2021-03-12 1:00 ` Stephen Rothwell
2021-03-26 1:18 ` Stephen Rothwell
2020-12-01 8:07 Stephen Rothwell
2020-12-01 14:55 ` Daniel Borkmann
2020-09-08 3:08 Stephen Rothwell
2020-09-08 17:54 ` Andrii Nakryiko
2020-08-21 1:11 Stephen Rothwell
2020-08-25 1:20 ` Stephen Rothwell
2020-08-25 1:25 ` Alexei Starovoitov
2020-08-25 3:04 ` Stephen Rothwell
2020-08-25 3:27 ` Alexei Starovoitov
2020-08-25 6:50 ` Stephen Rothwell
2020-08-25 14:33 ` Alexei Starovoitov
2020-08-25 21:10 ` Stephen Rothwell
2020-08-25 22:34 ` Alexei Starovoitov
2020-08-25 23:09 ` Stephen Rothwell
2020-07-14 2:22 Stephen Rothwell
2020-07-14 6:16 ` Jiri Olsa
2020-07-14 8:31 ` Jiri Olsa
2020-07-14 9:19 ` Geert Uytterhoeven
2019-07-01 4:57 Stephen Rothwell
2019-07-01 5:01 ` Stephen Rothwell
2019-04-18 1:57 Stephen Rothwell
2019-02-28 1:31 Stephen Rothwell
2019-02-28 2:18 ` Alexei Starovoitov
2018-10-03 3:18 Stephen Rothwell
2018-10-03 5:29 ` Joe Stringer
2018-09-07 0:19 Stephen Rothwell
2018-09-07 0:22 ` Alexei Starovoitov
2018-09-07 5:21 ` Björn Töpel
2018-09-07 5:45 ` Alexei Starovoitov
2017-12-13 1:32 Stephen Rothwell
2017-12-13 1:47 ` Alexei Starovoitov
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='CAFULd4aaOPYMpSWN=FNueoqXDKKfLu7P0NLr2DU1J2HKgxr_8A@mail.gmail.com' \
--to=ubizjak@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).