netdev - Re: [PATCH bpf-next] bpf: tcp: Limit calling some tcp cc functions to CONFIG_DYNAMIC

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] [day] [month] [year] [list]

Message-Id: <161706960839.12105.10125740091884845374.git-patchwork-notify@kernel.org>
Date:   Tue, 30 Mar 2021 02:00:08 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Martin KaFai Lau <kafai@...com>
Cc:     bpf@...r.kernel.org, ast@...nel.org, daniel@...earbox.net,
        kernel-team@...com, netdev@...r.kernel.org,
        xiyou.wangcong@...il.com, lmb@...udflare.com
Subject: Re: [PATCH bpf-next] bpf: tcp: Limit calling some tcp cc functions to
 CONFIG_DYNAMIC_FTRACE

Hello:

This patch was applied to bpf/bpf-next.git (refs/heads/master):

On Mon, 29 Mar 2021 15:13:57 -0700 you wrote:
> pahole currently only generates the btf_id for external function and
> ftrace-able function.  Some functions in the bpf_tcp_ca_kfunc_ids
> are static (e.g. cubictcp_init).  Thus, unless CONFIG_DYNAMIC_FTRACE
> is set, btf_ids for those functions will not be generated and the
> compilation fails during resolve_btfids.
> 
> This patch limits those functions to CONFIG_DYNAMIC_FTRACE.  I will
> address the pahole generation in a followup and then remove the
> CONFIG_DYNAMIC_FTRACE limitation.
> 
> [...]

Here is the summary with links:
  - [bpf-next] bpf: tcp: Limit calling some tcp cc functions to CONFIG_DYNAMIC_FTRACE
    https://git.kernel.org/bpf/bpf-next/c/7aae231ac93b

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