From: Yonghong Song <yonghong.song@linux.dev>
To: Ian Rogers <irogers@google.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <martin.lau@linux.dev>,
Eduard Zingerman <eddyz87@gmail.com>, Song Liu <song@kernel.org>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
Stanislav Fomichev <sdf@fomichev.me>, Hao Luo <haoluo@google.com>,
Jiri Olsa <jolsa@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Ingo Molnar <mingo@redhat.com>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Namhyung Kim <namhyung@kernel.org>,
Alexander Shishkin <alexander.shishkin@linux.intel.com>,
Adrian Hunter <adrian.hunter@intel.com>,
James Clark <james.clark@linaro.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v1 1/2] libbpf: Fix strict aliasing violations in hashmap
Date: Sat, 21 Mar 2026 08:40:05 -0700 [thread overview]
Message-ID: <20d77c80-6538-4dec-804c-156402c26534@linux.dev> (raw)
In-Reply-To: <20260321024446.692008-1-irogers@google.com>
On 3/20/26 7:44 PM, Ian Rogers wrote:
> The hashmap implementation contained strict aliasing violations.
> Specifically, the hashmap_cast_ptr(p) macro was casting pointers (such
> as void **) to long *, and these were subsequently dereferenced in
> functions like hashmap_insert(), hashmap_find(), and hashmap_delete().
>
> C's strict aliasing rules (C11 6.5/7) prohibit accessing an object
> through an lvalue of an incompatible type. Dereferencing a long * to
> write to a void * object is a violation, even if they share the same
> size, as they are not compatible types. This can lead to undefined
> behavior, especially with aggressive compiler optimizations.
Potentially this could be a concern. Did you actually find an issue
with it?
The linux kernel build has
KBUILD_CFLAGS += -fno-strict-aliasing
The libbpf does not have this flag. Maybe we should add '-fno-strict-aliasing'
for libbpf as well? This way, we can avoid any future potential
'strict aliasing' issues.
Note that bpf program (tools/testing/selftests/bpf/Makefile)
also has '-fno-strict-alaising' flag.
>
> Fix this by:
> 1. Updating hashmap_insert(), hashmap_find(), and hashmap_delete() to
> take void * for their output parameters (old_key, old_value, and
> value).
> 2. Modifying the implementation to use memcpy() and memset() for
> accessing these output parameters. Accessing an object as an array of
> characters (as done by memcpy) is a permitted exception to the
> strict aliasing rules.
> 3. Updating the hashmap_cast_ptr(p) macro to return void *, ensuring
> compatibility with the new function signatures while preserving the
> static assertion that ensures the pointed-to type matches the size of
> a long.
>
> Input parameters (key and value) remain as long, as they involve value
> conversion rather than incompatible pointer dereferencing, which is safe
> under strict aliasing rules.
>
> Signed-off-by: Ian Rogers <irogers@google.com>
> ---
> tools/lib/bpf/hashmap.c | 21 +++++++++++----------
> tools/lib/bpf/hashmap.h | 8 ++++----
> 2 files changed, 15 insertions(+), 14 deletions(-)
>
> diff --git a/tools/lib/bpf/hashmap.c b/tools/lib/bpf/hashmap.c
> index 140ee4055676..ef50d262a126 100644
> --- a/tools/lib/bpf/hashmap.c
> +++ b/tools/lib/bpf/hashmap.c
> @@ -8,6 +8,7 @@
> #include <stdint.h>
> #include <stdlib.h>
> #include <stdio.h>
> +#include <string.h>
> #include <errno.h>
> #include <linux/err.h>
> #include "hashmap.h"
> @@ -153,24 +154,24 @@ static bool hashmap_find_entry(const struct hashmap *map,
>
> int hashmap_insert(struct hashmap *map, long key, long value,
> enum hashmap_insert_strategy strategy,
> - long *old_key, long *old_value)
> + void *old_key, void *old_value)
> {
> struct hashmap_entry *entry;
> size_t h;
> int err;
>
> if (old_key)
> - *old_key = 0;
> + memset(old_key, 0, sizeof(long));
> if (old_value)
> - *old_value = 0;
> + memset(old_value, 0, sizeof(long));
>
> h = hash_bits(map->hash_fn(key, map->ctx), map->cap_bits);
> if (strategy != HASHMAP_APPEND &&
> hashmap_find_entry(map, key, h, NULL, &entry)) {
> if (old_key)
> - *old_key = entry->key;
> + memcpy(old_key, &entry->key, sizeof(long));
> if (old_value)
> - *old_value = entry->value;
> + memcpy(old_value, &entry->value, sizeof(long));
>
> if (strategy == HASHMAP_SET || strategy == HASHMAP_UPDATE) {
> entry->key = key;
> @@ -203,7 +204,7 @@ int hashmap_insert(struct hashmap *map, long key, long value,
> return 0;
> }
[...]
next prev parent reply other threads:[~2026-03-21 15:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-21 2:44 [PATCH v1 1/2] libbpf: Fix strict aliasing violations in hashmap Ian Rogers
2026-03-21 2:44 ` [PATCH v1 2/2] perf tools: " Ian Rogers
2026-03-21 12:37 ` [PATCH v1 1/2] libbpf: " sun jian
2026-03-21 15:40 ` Yonghong Song [this message]
2026-03-21 17:36 ` Kumar Kartikeya Dwivedi
2026-03-21 19:49 ` Alexei Starovoitov
2026-03-21 23:04 ` Ian Rogers
2026-03-21 23:08 ` Alexei Starovoitov
2026-03-21 23:10 ` Ian Rogers
2026-03-22 0:58 ` [PATCH v2 0/4] perf hashmap: Separate perf's hashmap code from libbpf Ian Rogers
2026-03-22 0:58 ` [PATCH v2 1/4] perf build: Don't check difference of perf and libbpf hashmap Ian Rogers
2026-03-22 0:58 ` [PATCH v2 2/4] perf hashmap: Rename hashmap to perf_hashmap to avoid libbpf conflict Ian Rogers
2026-03-22 0:58 ` [PATCH v2 3/4] perf hashmap: Fix strict aliasing violations in hashmap Ian Rogers
2026-03-22 0:58 ` [PATCH v2 4/4] perf hashmap: Remove errptr usage from hashmap Ian Rogers
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20d77c80-6538-4dec-804c-156402c26534@linux.dev \
--to=yonghong.song@linux.dev \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=irogers@google.com \
--cc=james.clark@linaro.org \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=martin.lau@linux.dev \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=sdf@fomichev.me \
--cc=song@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox