From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: stable@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
patches@lists.linux.dev, David Michael <fedora.dm0@gmail.com>,
Daniel Borkmann <daniel@iogearbox.net>,
Stanislav Fomichev <sdf@google.com>,
Alan Maguire <alan.maguire@oracle.com>
Subject: [PATCH 6.0 04/16] libbpf: Fix uninitialized warning in btf_dump_dump_type_data
Date: Thu, 15 Dec 2022 19:10:48 +0100 [thread overview]
Message-ID: <20221215172908.338365689@linuxfoundation.org> (raw)
In-Reply-To: <20221215172908.162858817@linuxfoundation.org>
From: David Michael <fedora.dm0@gmail.com>
commit dfd0afbf151d85411b371e841f62b81ee5d1ca54 upstream.
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)
| ^
Fixes: 920d16af9b42 ("libbpf: BTF dumper support for typed data")
Signed-off-by: David Michael <fedora.dm0@gmail.com>
Signed-off-by: Daniel Borkmann <daniel@iogearbox.net>
Acked-by: Stanislav Fomichev <sdf@google.com>
Acked-by: Alan Maguire <alan.maguire@oracle.com>
Link: https://lore.kernel.org/bpf/87zgcu60hq.fsf@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
tools/lib/bpf/btf_dump.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/tools/lib/bpf/btf_dump.c
+++ b/tools/lib/bpf/btf_dump.c
@@ -1963,7 +1963,7 @@ static int btf_dump_struct_data(struct b
{
const struct btf_member *m = btf_members(t);
__u16 n = btf_vlen(t);
- int i, err;
+ int i, err = 0;
/* note that we increment depth before calling btf_dump_print() below;
* this is intentional. btf_dump_data_newline() will not print a
next prev parent reply other threads:[~2022-12-15 18:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-15 18:10 [PATCH 6.0 00/16] 6.0.14-rc1 review Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 01/16] rtc: cmos: Fix event handler registration ordering issue Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 02/16] rtc: cmos: Fix wake alarm breakage Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 03/16] x86/vdso: Conditionally export __vdso_sgx_enter_enclave() Greg Kroah-Hartman
2022-12-15 18:10 ` Greg Kroah-Hartman [this message]
2022-12-15 18:10 ` [PATCH 6.0 05/16] rtc: cmos: fix build on non-ACPI platforms Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 06/16] ASoC: fsl_micfil: explicitly clear software reset bit Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 07/16] ASoC: fsl_micfil: explicitly clear CHnF flags Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 08/16] ASoC: ops: Check bounds for second channel in snd_soc_put_volsw_sx() Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 09/16] libbpf: Use page size as max_entries when probing ring buffer map Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 10/16] pinctrl: meditatek: Startup with the IRQs disabled Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 11/16] can: sja1000: fix size of OCR_MODE_MASK define Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 12/16] can: mcba_usb: Fix termination command argument Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 13/16] net: fec: dont reset irq coalesce settings to defaults on "ip link up" Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 14/16] ASoC: cs42l51: Correct PGA Volume minimum value Greg Kroah-Hartman
2022-12-15 18:10 ` [PATCH 6.0 15/16] perf: Fix perf_pending_task() UaF Greg Kroah-Hartman
2022-12-15 18:11 ` [PATCH 6.0 16/16] nvme-pci: clear the prp2 field when not used Greg Kroah-Hartman
2022-12-15 23:45 ` [PATCH 6.0 00/16] 6.0.14-rc1 review Shuah Khan
2022-12-16 9:51 ` Bagas Sanjaya
2022-12-16 10:08 ` Allen Pais
2022-12-16 10:28 ` Naresh Kamboju
2022-12-16 11:13 ` Ron Economos
2022-12-16 13:05 ` Jon Hunter
2022-12-16 13:15 ` Sudip Mukherjee (Codethink)
2022-12-16 20:57 ` Florian Fainelli
2022-12-16 22:24 ` Guenter Roeck
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=20221215172908.338365689@linuxfoundation.org \
--to=gregkh@linuxfoundation.org \
--cc=alan.maguire@oracle.com \
--cc=daniel@iogearbox.net \
--cc=fedora.dm0@gmail.com \
--cc=patches@lists.linux.dev \
--cc=sdf@google.com \
--cc=stable@vger.kernel.org \
/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