[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <160702620653.3826.6715254971435173910.git-patchwork-notify@kernel.org>
Date: Thu, 03 Dec 2020 20:10:06 +0000
From: patchwork-bot+netdevbpf@...nel.org
To: Toke Høiland-Jørgensen <toke@...hat.com>@ci.codeaurora.org
Cc: daniel@...earbox.net, ast@...com, andrii@...nel.org,
bpf@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH bpf v3] libbpf: sanitise map names before pinning
Hello:
This patch was applied to bpf/bpf-next.git (refs/heads/master):
On Thu, 3 Dec 2020 10:33:06 +0100 you wrote:
> When we added sanitising of map names before loading programs to libbpf, we
> still allowed periods in the name. While the kernel will accept these for
> the map names themselves, they are not allowed in file names when pinning
> maps. This means that bpf_object__pin_maps() will fail if called on an
> object that contains internal maps (such as sections .rodata).
>
> Fix this by replacing periods with underscores when constructing map pin
> paths. This only affects the paths generated by libbpf when
> bpf_object__ping_maps() is called with a path argument. Any pin paths set
> by bpf_map__set_pin_path() are unaffected, and it will still be up to the
> caller to avoid invalid characters in those.
>
> [...]
Here is the summary with links:
- [bpf,v3] libbpf: sanitise map names before pinning
https://git.kernel.org/bpf/bpf-next/c/9cf309c56f79
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