netdev - Re: [PATCH bpf-next 1/2] libbpf: Use IS_ERR_OR_NULL() in hashmap_

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: <164159281077.23296.8769148718825057618.git-patchwork-notify@kernel.org>
Date:   Fri, 07 Jan 2022 22:00:10 +0000
From:   patchwork-bot+netdevbpf@...nel.org
To:     Mauricio Vásquez <mauricio@...volk.io>@ci.codeaurora.org
Cc:     netdev@...r.kernel.org, bpf@...r.kernel.org, ast@...nel.org,
        daniel@...earbox.net, andrii@...nel.org, quentin@...valent.com
Subject: Re: [PATCH bpf-next 1/2] libbpf: Use IS_ERR_OR_NULL() in hashmap__free()

Hello:

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

On Fri,  7 Jan 2022 10:26:19 -0500 you wrote:
> hashmap__new() uses ERR_PTR() to return an error so it's better to
> use IS_ERR_OR_NULL() in order to check the pointer before calling
> free(). This will prevent freeing an invalid pointer if somebody calls
> hashmap__free() with the result of a failed hashmap__new() call.
> 
> Signed-off-by: Mauricio Vásquez <mauricio@...volk.io>
> 
> [...]

Here is the summary with links:
  - [bpf-next,1/2] libbpf: Use IS_ERR_OR_NULL() in hashmap__free()
    https://git.kernel.org/bpf/bpf-next/c/d793c2eb5dbc
  - [bpf-next,2/2] bpftool: Fix error check when calling hashmap__new()
    https://git.kernel.org/bpf/bpf-next/c/2318517920d1

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