From: Yonghong Song <yhs@meta.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>
Cc: bpf@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>
Subject: Re: [PATCH bpf-next] libbpf: Fix overflow detection when dumping bitfields
Date: Fri, 28 Apr 2023 10:30:51 -0700 [thread overview]
Message-ID: <006349b9-7cec-bf02-2732-90aaf614f342@meta.com> (raw)
In-Reply-To: <20230428155035.530862-1-iii@linux.ibm.com>
On 4/28/23 8:50 AM, Ilya Leoshkevich wrote:
> btf_dump test fails on s390x with the following error:
>
> unexpected return value dumping fs_context: actual -7 != expected 280
>
> This happens when processing the fs_context.phase member: its type size
> is 4, but there are less bytes left until the end of the struct. The
> problem is that btf_dump_type_data_check_overflow() does not handle
> bitfields.
>
> Add bitfield support; make sure that byte boundaries, which are
> computed from bit boundaries, are rounded up.
Ilya, Martin has submitted a patch yesterday to fix the issue:
https://lore.kernel.org/bpf/20230428013638.1581263-1-martin.lau@linux.dev/
>
> Fixes: 920d16af9b42 ("libbpf: BTF dumper support for typed data")
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
> tools/lib/bpf/btf_dump.c | 12 +++++++++---
> 1 file changed, 9 insertions(+), 3 deletions(-)
>
> diff --git a/tools/lib/bpf/btf_dump.c b/tools/lib/bpf/btf_dump.c
> index 580985ee5545..f8b538e8d753 100644
> --- a/tools/lib/bpf/btf_dump.c
> +++ b/tools/lib/bpf/btf_dump.c
> @@ -2250,9 +2250,11 @@ static int btf_dump_type_data_check_overflow(struct btf_dump *d,
> const struct btf_type *t,
> __u32 id,
> const void *data,
> - __u8 bits_offset)
> + __u8 bits_offset,
> + __u8 bit_sz)
> {
> __s64 size = btf__resolve_size(d->btf, id);
> + const void *end;
>
> if (size < 0 || size >= INT_MAX) {
> pr_warn("unexpected size [%zu] for id [%u]\n",
> @@ -2280,7 +2282,11 @@ static int btf_dump_type_data_check_overflow(struct btf_dump *d,
> case BTF_KIND_PTR:
> case BTF_KIND_ENUM:
> case BTF_KIND_ENUM64:
> - if (data + bits_offset / 8 + size > d->typed_dump->data_end)
> + if (bit_sz)
> + end = data + (bits_offset + bit_sz + 7) / 8;
> + else
> + end = data + (bits_offset + 7) / 8 + size;
> + if (end > d->typed_dump->data_end)
> return -E2BIG;
> break;
> default:
> @@ -2407,7 +2413,7 @@ static int btf_dump_dump_type_data(struct btf_dump *d,
> {
> int size, err = 0;
>
> - size = btf_dump_type_data_check_overflow(d, t, id, data, bits_offset);
> + size = btf_dump_type_data_check_overflow(d, t, id, data, bits_offset, bit_sz);
> if (size < 0)
> return size;
> err = btf_dump_type_data_check_zero(d, t, id, data, bits_offset, bit_sz);
prev parent reply other threads:[~2023-04-28 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-28 15:50 [PATCH bpf-next] libbpf: Fix overflow detection when dumping bitfields Ilya Leoshkevich
2023-04-28 17:30 ` Yonghong Song [this message]
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=006349b9-7cec-bf02-2732-90aaf614f342@meta.com \
--to=yhs@meta.com \
--cc=agordeev@linux.ibm.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=iii@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