From: Mykyta Yatsenko <mykyta.yatsenko5@gmail.com>
To: Amery Hung <ameryhung@gmail.com>, bpf@vger.kernel.org
Cc: alexei.starovoitov@gmail.com, andrii@kernel.org,
daniel@iogearbox.net, eddyz87@gmail.com, memxor@gmail.com,
ameryhung@gmail.com, kernel-team@meta.com
Subject: Re: [PATCH bpf-next v1 1/3] selftests/bpf: Fix task_local_data data allocation size
Date: Thu, 26 Mar 2026 16:17:57 +0000 [thread overview]
Message-ID: <87ikaiimyy.fsf@gmail.com> (raw)
In-Reply-To: <20260326052437.590158-2-ameryhung@gmail.com>
Amery Hung <ameryhung@gmail.com> writes:
> Currently, when allocating memory for data, size of tld_data_u->start
> is not taken into account. This may cause OOB access. Fixed it by adding
> the non-flexible array part of tld_datg_u.
>
> Besides, explicitly align tld_data_u->data to 8 bytes in case some
> fields are added before data in the future. It could break the
> assumption that every data field is 8 byte aligned and
> sizeof(tld_data_u) will no longer be equal to
> offsetof(struct tld_data_u, data), which we use interchangeably.
>
> Signed-off-by: Amery Hung <ameryhung@gmail.com>
> ---
> .../selftests/bpf/prog_tests/task_local_data.h | 12 +++++++-----
> 1 file changed, 7 insertions(+), 5 deletions(-)
>
> diff --git a/tools/testing/selftests/bpf/prog_tests/task_local_data.h b/tools/testing/selftests/bpf/prog_tests/task_local_data.h
> index 7819f318b2fb..a52d8b549425 100644
> --- a/tools/testing/selftests/bpf/prog_tests/task_local_data.h
> +++ b/tools/testing/selftests/bpf/prog_tests/task_local_data.h
> @@ -90,7 +90,7 @@ typedef struct {
>
> struct tld_metadata {
> char name[TLD_NAME_LEN];
> - _Atomic __u16 size;
> + _Atomic __u16 size; /* size of tld_data_u->data */
> };
>
> struct tld_meta_u {
> @@ -101,7 +101,7 @@ struct tld_meta_u {
>
> struct tld_data_u {
> __u64 start; /* offset of tld_data_u->data in a page */
> - char data[];
> + char data[] __attribute__((aligned(8)));
> };
>
> struct tld_map_value {
> @@ -158,6 +158,7 @@ static int __tld_init_data_p(int map_fd)
> struct tld_data_u *data;
> void *data_alloc = NULL;
> int err, tid_fd = -1;
> + size_t size;
>
> tid_fd = syscall(SYS_pidfd_open, sys_gettid(), O_EXCL);
> if (tid_fd < 0) {
> @@ -173,9 +174,10 @@ static int __tld_init_data_p(int map_fd)
> * tld_meta_p->size = TLD_DYN_DATA_SIZE +
> * total size of TLDs defined via TLD_DEFINE_KEY()
> */
> - data_alloc = (use_aligned_alloc || tld_meta_p->size * 2 >= TLD_PAGE_SIZE) ?
> - aligned_alloc(TLD_PAGE_SIZE, tld_meta_p->size) :
> - malloc(tld_meta_p->size * 2);
> + size = tld_meta_p->size + sizeof(struct tld_data_u);
> + data_alloc = (use_aligned_alloc || size * 2 >= TLD_PAGE_SIZE) ?
> + aligned_alloc(TLD_PAGE_SIZE, size) :
> + malloc(size * 2);
It looks like there is no point having Patch 1 separately, most of it is
overwritten in the Patch 2, I understand you want to have fix and
simplification separately, but is it really worth it for this selftest.
> if (!data_alloc) {
> err = -ENOMEM;
> goto out;
> --
> 2.52.0
next prev parent reply other threads:[~2026-03-26 16:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-26 5:24 [PATCH bpf-next v1 0/3] Task local data bug fixes and improvement Amery Hung
2026-03-26 5:24 ` [PATCH bpf-next v1 1/3] selftests/bpf: Fix task_local_data data allocation size Amery Hung
2026-03-26 10:27 ` sun jian
2026-03-26 15:56 ` Amery Hung
2026-03-26 16:17 ` Mykyta Yatsenko [this message]
2026-03-26 20:32 ` Amery Hung
2026-03-26 5:24 ` [PATCH bpf-next v1 2/3] selftests/bpf: Simplify task_local_data memory allocation Amery Hung
2026-03-27 16:36 ` Mykyta Yatsenko
2026-03-27 20:56 ` Amery Hung
2026-03-27 21:15 ` Mykyta Yatsenko
2026-03-26 5:24 ` [PATCH bpf-next v1 3/3] selftests/bpf: Make sure TLD_DEFINE_KEY runs first Amery Hung
2026-03-27 16:56 ` Mykyta Yatsenko
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=87ikaiimyy.fsf@gmail.com \
--to=mykyta.yatsenko5@gmail.com \
--cc=alexei.starovoitov@gmail.com \
--cc=ameryhung@gmail.com \
--cc=andrii@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=kernel-team@meta.com \
--cc=memxor@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.