BPF List
 help / color / mirror / Atom feed
From: Alan Maguire <alan.maguire@oracle.com>
To: Ian Rogers <irogers@google.com>,
	Quentin Monnet <quentin@isovalent.com>,
	Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	Martin KaFai Lau <martin.lau@linux.dev>,
	Song Liu <song@kernel.org>,
	Yonghong Song <yonghong.song@linux.dev>,
	John Fastabend <john.fastabend@gmail.com>,
	KP Singh <kpsingh@kernel.org>,
	Stanislav Fomichev <sdf@google.com>, Hao Luo <haoluo@google.com>,
	Jiri Olsa <jolsa@kernel.org>,
	bpf@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] bpftool: Align output skeleton ELF code
Date: Tue, 3 Oct 2023 09:58:09 +0100	[thread overview]
Message-ID: <0f367aff-b818-d59b-513a-cadd6fa67782@oracle.com> (raw)
In-Reply-To: <CAP-5=fWmxKHLGnQqBjUb8MZFak6YaKMPGKKWwBiCc6XWZbVPDw@mail.gmail.com>

On 03/10/2023 05:29, Ian Rogers wrote:
> On Mon, Oct 2, 2023 at 3:32 PM Ian Rogers <irogers@google.com> wrote:
>>
>> libbpf accesses the ELF data requiring at least 8 byte alignment,
>> however, the data is generated into a C string that doesn't guarantee
>> alignment. Fix this by assigning to an aligned char array, use sizeof
>> on the array, less one for the \0 terminator.
>>
>> Signed-off-by: Ian Rogers <irogers@google.com>

this looks like a great catch to me!

Reviewed-by: Alan Maguire <alan.maguire@oracle.com>

>> ---
> 
> Perhaps this could have a fixes tag:
> Fixes: d510296d331a ("bpftool: Use syscall/loader program in "prog
> load" and "gen skeleton" command.")
> 

Yep, or perhaps

Fixes: a6cc6b34b93e ("bpftool: Provide a helper method for accessing
skeleton's embedded ELF data")



> The unaligned problem was seen in perf's offcpu code as well as bcc's
> libbpf_tools. I didn't see problems with map data and opts data, but
> inspection of the code shows they likely have the same issue. I was
> testing with -fsanitize=alignment and
> -fsanitize-undefined-trap-on-error.
> 
> Thanks,
> Ian
> 
>>  tools/bpf/bpftool/gen.c | 15 +++++++++------
>>  1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/tools/bpf/bpftool/gen.c b/tools/bpf/bpftool/gen.c
>> index 2883660d6b67..b8ebcee9bc56 100644
>> --- a/tools/bpf/bpftool/gen.c
>> +++ b/tools/bpf/bpftool/gen.c
>> @@ -1209,7 +1209,7 @@ static int do_skeleton(int argc, char **argv)
>>         codegen("\
>>                 \n\
>>                                                                             \n\
>> -                       s->data = (void *)%2$s__elf_bytes(&s->data_sz);     \n\
>> +                       s->data = (void *)%1$s__elf_bytes(&s->data_sz);     \n\
>>                                                                             \n\
>>                         obj->skeleton = s;                                  \n\
>>                         return 0;                                           \n\
>> @@ -1218,12 +1218,12 @@ static int do_skeleton(int argc, char **argv)
>>                         return err;                                         \n\
>>                 }                                                           \n\
>>                                                                             \n\
>> -               static inline const void *%2$s__elf_bytes(size_t *sz)       \n\
>> +               static inline const void *%1$s__elf_bytes(size_t *sz)       \n\
>>                 {                                                           \n\
>> -                       *sz = %1$d;                                         \n\
>> -                       return (const void *)\"\\                           \n\
>> -               "
>> -               , file_sz, obj_name);
>> +                       static const char data[] __attribute__((__aligned__(8))) = \"\\\n\
>> +               ",
>> +               obj_name
>> +       );
>>
>>         /* embed contents of BPF object file */
>>         print_hex(obj_data, file_sz);
>> @@ -1231,6 +1231,9 @@ static int do_skeleton(int argc, char **argv)
>>         codegen("\
>>                 \n\
>>                 \";                                                         \n\
>> +                                                                           \n\
>> +                       *sz = sizeof(data) - 1;                             \n\
>> +                       return (const void *)data;                          \n\
>>                 }                                                           \n\
>>                                                                             \n\
>>                 #ifdef __cplusplus                                          \n\
>> --
>> 2.42.0.582.g8ccd20d70d-goog
>>
> 

      reply	other threads:[~2023-10-03  8:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-02 22:32 [PATCH v1] bpftool: Align output skeleton ELF code Ian Rogers
2023-10-03  4:29 ` Ian Rogers
2023-10-03  8:58   ` Alan Maguire [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=0f367aff-b818-d59b-513a-cadd6fa67782@oracle.com \
    --to=alan.maguire@oracle.com \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=haoluo@google.com \
    --cc=irogers@google.com \
    --cc=john.fastabend@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=kpsingh@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=martin.lau@linux.dev \
    --cc=quentin@isovalent.com \
    --cc=sdf@google.com \
    --cc=song@kernel.org \
    --cc=yonghong.song@linux.dev \
    /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