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: <166380721444.7808.9756811358401247254.git-patchwork-notify@kernel.org>
Date:   Thu, 22 Sep 2022 00:40:14 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Tao Chen <chentao.kernel@...ux.alibaba.com>
Cc:     ast@...nel.org, daniel@...earbox.net, andrii@...nel.org,
        kafai@...com, yhs@...com, songliubraving@...com,
        john.fastabend@...il.com, kpsingh@...nel.org,
        netdev@...r.kernel.org, bpf@...r.kernel.org,
        linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] libbpf: Support raw btf placed in the default path

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Andrii Nakryiko <andrii@...nel.org>:

On Tue, 13 Sep 2022 00:43:00 +0800 you wrote:
> Now only elf btf can be placed in the default path(/boot), raw
> btf should also can be there.
> 
> Signed-off-by: Tao Chen <chentao.kernel@...ux.alibaba.com>
> ---
> v2->v1: Remove the locations[i].raw_btf check
> 
> [...]

Here is the summary with links:
  - [v2] libbpf: Support raw btf placed in the default path
    https://git.kernel.org/bpf/bpf-next/c/01f2e36c959c

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