linux-kernel - Re: [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <166760041503.11044.8727035971633367268.git-patchwork-notify@kernel.org>
Date:   Fri, 04 Nov 2022 22:20:15 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Peter Zijlstra <peterz@...radead.org>
Cc:     olsajiri@...il.com, ast@...nel.org, daniel@...earbox.net,
        linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
        bpf@...r.kernel.org, bjorn@...nel.org, toke@...hat.com,
        David.Laight@...lab.com, rostedt@...dmis.org
Subject: Re: [PATCH 0/2] bpf: Yet another approach to fix the BPF dispatcher thing

Hello:

This series was applied to bpf/bpf.git (master)
by Daniel Borkmann <daniel@...earbox.net>:

On Thu, 03 Nov 2022 13:00:12 +0100 you wrote:
> Hi!
> 
> Even thought the __attribute__((patchable_function_entry())) solution to the
> BPF dispatcher woes works, it turns out to not be supported by the whole range
> of ageing compilers we support. Specifically this attribute seems to be GCC-8
> and later.
> 
> [...]

Here is the summary with links:
  - [1/2] bpf: Revert ("Fix dispatcher patchable function entry to 5 bytes nop")
    (no matching commit)
  - [2/2] bpf: Convert BPF_DISPATCHER to use static_call() (not ftrace)
    https://git.kernel.org/bpf/bpf/c/c86df29d11df

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html