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: <161677740966.24745.8034280482813674858.git-patchwork-notify@kernel.org>
Date:   Fri, 26 Mar 2021 16:50:09 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Andrii Nakryiko <andrii@...nel.org>
Cc:     bpf@...r.kernel.org, netdev@...r.kernel.org, ast@...com,
        daniel@...earbox.net, kernel-team@...com, yhs@...com,
        ast@...nel.org
Subject: Re: [PATCH v2 bpf-next] libbpf: preserve empty DATASEC BTFs during static
 linking

Hello:

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

On Thu, 25 Mar 2021 21:30:36 -0700 you wrote:
> Ensure that BPF static linker preserves all DATASEC BTF types, even if some of
> them might not have any variable information at all. This may happen if the
> compiler promotes local initialized variable contents into .rodata section and
> there are no global or static functions in the program.
> 
> For example,
> 
> [...]

Here is the summary with links:
  - [v2,bpf-next] libbpf: preserve empty DATASEC BTFs during static linking
    https://git.kernel.org/bpf/bpf-next/c/36e798516078

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


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ