All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <olsajiri@gmail.com>
To: David Faust <david.faust@oracle.com>
Cc: bpf@vger.kernel.org
Subject: Re: [PATCH bpf-next] libbpf: avoid mmap for size 0 sections
Date: Thu, 28 Jul 2022 16:15:50 +0200	[thread overview]
Message-ID: <YuKaFiZ+ksB5f0Ye@krava> (raw)
In-Reply-To: <20220727204808.13210-1-david.faust@oracle.com>

On Wed, Jul 27, 2022 at 01:48:08PM -0700, David Faust wrote:
> When populating maps in bpf_object__init_global_data_maps(), recognized
> sections with no data (e.g. a .bss with size 0) lead to an mmap of 0
> bytes which fails with EINVAL.
> 
> Add a check to skip mapping sections which are present, but empty.
> 
> Signed-off-by: David Faust <david.faust@oracle.com>
> ---
>  tools/lib/bpf/libbpf.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/tools/lib/bpf/libbpf.c b/tools/lib/bpf/libbpf.c
> index b01fe01b0761..4e7ceb4f5a27 100644
> --- a/tools/lib/bpf/libbpf.c
> +++ b/tools/lib/bpf/libbpf.c
> @@ -1642,6 +1642,10 @@ static int bpf_object__init_global_data_maps(struct bpf_object *obj)
>  	for (sec_idx = 1; sec_idx < obj->efile.sec_cnt; sec_idx++) {
>  		sec_desc = &obj->efile.secs[sec_idx];
>  
> +		/* Skip recognized sections with size 0. */
> +		if (sec_desc->data && sec_desc->data->d_size == 0)
> +		  continue;

nit missing tab indent

also we seem to check for size in bpf_object__elf_collect
before adding SEC_DATA/SEC_RODATA but not SEC_BSS

I think the check should be rather in bpf_object__elf_collect
before we add the desc for it

jirka

> +
>  		switch (sec_desc->sec_type) {
>  		case SEC_DATA:
>  			sec_name = elf_sec_name(obj, elf_sec_by_idx(obj, sec_idx));
> -- 
> 2.36.1
> 

  reply	other threads:[~2022-07-28 14:15 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-27 20:48 [PATCH bpf-next] libbpf: avoid mmap for size 0 sections David Faust
2022-07-28 14:15 ` Jiri Olsa [this message]
2022-07-28 19:29   ` David Faust

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=YuKaFiZ+ksB5f0Ye@krava \
    --to=olsajiri@gmail.com \
    --cc=bpf@vger.kernel.org \
    --cc=david.faust@oracle.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.