[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHk-=wheGrBxOfMpWhQg1iswCKYig8vADnFVsA4oFWTY9NU5jA@mail.gmail.com>
Date: Mon, 21 Mar 2022 16:01:45 -0700
From: Linus Torvalds <torvalds@...ux-foundation.org>
To: Alexei Starovoitov <alexei.starovoitov@...il.com>
Cc: David Miller <davem@...emloft.net>,
Daniel Borkmann <daniel@...earbox.net>,
Peter Zijlstra <peterz@...radead.org>,
Steven Rostedt <rostedt@...dmis.org>,
Masami Hiramatsu <mhiramat@...nel.org>,
Jakub Kicinski <kuba@...nel.org>,
Andrii Nakryiko <andrii@...nel.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Netdev <netdev@...r.kernel.org>, bpf <bpf@...r.kernel.org>,
Kernel Team <kernel-team@...com>
Subject: Re: pull-request: bpf-next 2022-03-21
On Mon, Mar 21, 2022 at 3:46 PM Alexei Starovoitov
<alexei.starovoitov@...il.com> wrote:
>
> The following pull-request contains BPF updates for your *net-next* tree.
No
This is the tree that contains bad architecture code that was NAK'ed
by both x86 and arm64 people respectively.
In particular, I think it's this part:
> Masami Hiramatsu (11):
> fprobe: Add ftrace based probe APIs
> rethook: Add a generic return hook
> rethook: x86: Add rethook x86 implementation
> arm64: rethook: Add arm64 rethook implementation
> powerpc: Add rethook support
> ARM: rethook: Add rethook arm implementation
> fprobe: Add exit_handler support
> fprobe: Add sample program for fprobe
> fprobe: Introduce FPROBE_FL_KPROBE_SHARED flag for fprobe
> docs: fprobe: Add fprobe description to ftrace-use.rst
> fprobe: Add a selftest for fprobe
That was added very late to the linux-next tree, and that causes build
warnings because of interactions with other changes.
Not ok.
Linus
Powered by blists - more mailing lists