From: Sam James <sam@gentoo.org>
To: Alan Maguire <alan.maguire@oracle.com>
Cc: "Alexei Starovoitov" <ast@kernel.org>,
"Daniel Borkmann" <daniel@iogearbox.net>,
"Andrii Nakryiko" <andrii@kernel.org>,
"Martin KaFai Lau" <martin.lau@linux.dev>,
"Eduard Zingerman" <eddyz87@gmail.com>,
"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@fomichev.me>,
"Hao Luo" <haoluo@google.com>, "Jiri Olsa" <jolsa@kernel.org>,
"Nathan Chancellor" <nathan@kernel.org>,
"Nick Desaulniers" <ndesaulniers@google.com>,
"Bill Wendling" <morbo@google.com>,
"Justin Stitt" <justinstitt@google.com>,
"Jose E . Marchesi" <jose.marchesi@oracle.com>,
"Andrew Pinski" <quic_apinski@quicinc.com>,
"Kacper Słomiński" <kacper.slominski72@gmail.com>,
"Arsen Arsenović" <arsen@gentoo.org>,
bpf@vger.kernel.org, linux-kernel@vger.kernel.org,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] libbpf: workaround -Wmaybe-uninitialized false positive
Date: Mon, 12 Aug 2024 11:40:58 +0100 [thread overview]
Message-ID: <87mslija6d.fsf@gentoo.org> (raw)
In-Reply-To: <3c9e6cbe-f768-48b1-9e37-779971fd1146@oracle.com> (Alan Maguire's message of "Fri, 9 Aug 2024 18:48:32 +0100")
Alan Maguire <alan.maguire@oracle.com> writes:
> On 09/08/2024 18:26, Sam James wrote:
>> In `elf_close`, we get this with GCC 15 -O3 (at least):
> [...]
>
> Would just initializing struct elf_fd be enough to silence the error
> perhaps, i.e.
Yeah, that WFM. Thanks, sent v3.
prev parent reply other threads:[~2024-08-12 10:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-09 17:26 [PATCH v2] libbpf: workaround -Wmaybe-uninitialized false positive Sam James
2024-08-09 17:48 ` Alan Maguire
2024-08-12 10:40 ` Sam James [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=87mslija6d.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=alan.maguire@oracle.com \
--cc=andrii@kernel.org \
--cc=arsen@gentoo.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=eddyz87@gmail.com \
--cc=haoluo@google.com \
--cc=john.fastabend@gmail.com \
--cc=jolsa@kernel.org \
--cc=jose.marchesi@oracle.com \
--cc=justinstitt@google.com \
--cc=kacper.slominski72@gmail.com \
--cc=kpsingh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=martin.lau@linux.dev \
--cc=morbo@google.com \
--cc=nathan@kernel.org \
--cc=ndesaulniers@google.com \
--cc=quic_apinski@quicinc.com \
--cc=sdf@fomichev.me \
--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 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.