From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii.nakryiko@gmail.com>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH bpf-next v2 4/4] libbpf: Fix ptr_is_aligned() usages
Date: Wed, 13 Oct 2021 18:09:02 +0200 [thread overview]
Message-ID: <20211013160902.428340-5-iii@linux.ibm.com> (raw)
In-Reply-To: <20211013160902.428340-1-iii@linux.ibm.com>
Currently ptr_is_aligned() takes size, and not alignment, as a
parameter, which may be overly pessimistic e.g. for __i128 on s390,
which must be only 8-byte aligned. Fix by using btf__align_of() where
possible - one notable exception is ptr_sz, for which there is no
corresponding type.
Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
---
tools/lib/bpf/btf_dump.c | 12 +++++-------
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/tools/lib/bpf/btf_dump.c b/tools/lib/bpf/btf_dump.c
index 25ce60828e8d..da345520892f 100644
--- a/tools/lib/bpf/btf_dump.c
+++ b/tools/lib/bpf/btf_dump.c
@@ -1657,9 +1657,9 @@ static int btf_dump_base_type_check_zero(struct btf_dump *d,
return 0;
}
-static bool ptr_is_aligned(const void *data, int data_sz)
+static bool ptr_is_aligned(const void *data, int alignment)
{
- return ((uintptr_t)data) % data_sz == 0;
+ return ((uintptr_t)data) % alignment == 0;
}
static int btf_dump_int_data(struct btf_dump *d,
@@ -1681,7 +1681,7 @@ static int btf_dump_int_data(struct btf_dump *d,
/* handle packed int data - accesses of integers not aligned on
* int boundaries can cause problems on some platforms.
*/
- if (!ptr_is_aligned(data, sz)) {
+ if (!ptr_is_aligned(data, btf__align_of(d->btf, type_id))) {
memcpy(buf, data, sz);
data = buf;
}
@@ -1770,7 +1770,7 @@ static int btf_dump_float_data(struct btf_dump *d,
int sz = t->size;
/* handle unaligned data; copy to local union */
- if (!ptr_is_aligned(data, sz)) {
+ if (!ptr_is_aligned(data, btf__align_of(d->btf, type_id))) {
memcpy(&fl, data, sz);
flp = &fl;
}
@@ -1953,10 +1953,8 @@ static int btf_dump_get_enum_value(struct btf_dump *d,
__u32 id,
__s64 *value)
{
- int sz = t->size;
-
/* handle unaligned enum value */
- if (!ptr_is_aligned(data, sz)) {
+ if (!ptr_is_aligned(data, btf__align_of(d->btf, id))) {
__u64 val;
int err;
--
2.31.1
next prev parent reply other threads:[~2021-10-13 16:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 16:08 [PATCH bpf-next v2 0/4] btf_dump fixes for s390 Ilya Leoshkevich
2021-10-13 16:08 ` [PATCH bpf-next v2 1/4] selftests/bpf: Use cpu_number only on arches that have it Ilya Leoshkevich
2021-10-13 16:09 ` [PATCH bpf-next v2 2/4] libbpf: Fix dumping big-endian bitfields Ilya Leoshkevich
2021-10-13 16:09 ` [PATCH bpf-next v2 3/4] libbpf: Fix dumping non-aligned __int128 Ilya Leoshkevich
2021-10-13 16:09 ` Ilya Leoshkevich [this message]
2021-10-20 18:44 ` [PATCH bpf-next v2 4/4] libbpf: Fix ptr_is_aligned() usages Andrii Nakryiko
2021-10-20 23:02 ` Ilya Leoshkevich
2021-10-20 23:10 ` Andrii Nakryiko
2021-10-21 10:29 ` Ilya Leoshkevich
2021-10-20 18:48 ` [PATCH bpf-next v2 0/4] btf_dump fixes for s390 Andrii Nakryiko
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=20211013160902.428340-5-iii@linux.ibm.com \
--to=iii@linux.ibm.com \
--cc=andrii.nakryiko@gmail.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
/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;
as well as URLs for NNTP newsgroup(s).