All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: David Michael <fedora.dm0@gmail.com>
Cc: andrii@kernel.org, bpf@vger.kernel.org
Subject: Re: [PATCH] libbpf: Fix uninitialized warning in btf_dump_dump_type_data
Date: Mon, 14 Nov 2022 18:10:15 +0000	[thread overview]
Message-ID: <166844941598.9787.7733977878486335129.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <87zgcu60hq.fsf@gmail.com>

Hello:

This patch was applied to bpf/bpf-next.git (master)
by Daniel Borkmann <daniel@iogearbox.net>:

On Sun, 13 Nov 2022 15:52:17 -0500 you wrote:
> GCC 11.3.0 fails to compile btf_dump.c due to the following error,
> which seems to originate in btf_dump_struct_data where the returned
> value would be uninitialized if btf_vlen returns zero.
> 
> btf_dump.c: In function ‘btf_dump_dump_type_data’:
> btf_dump.c:2363:12: error: ‘err’ may be used uninitialized in this function [-Werror=maybe-uninitialized]
>  2363 |         if (err < 0)
>       |            ^
> 
> [...]

Here is the summary with links:
  - libbpf: Fix uninitialized warning in btf_dump_dump_type_data
    https://git.kernel.org/bpf/bpf-next/c/dfd0afbf151d

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2022-11-14 18:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-13 20:52 [PATCH] libbpf: Fix uninitialized warning in btf_dump_dump_type_data David Michael
2022-11-14 17:21 ` sdf
2022-11-14 17:54   ` Alan Maguire
2022-11-14 18:10 ` patchwork-bot+netdevbpf [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=166844941598.9787.7733977878486335129.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --cc=andrii@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=fedora.dm0@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.