From: David Howells <dhowells@redhat.com>
To: Naresh Kamboju <naresh.kamboju@linaro.org>
Cc: dhowells@redhat.com, netfs@lists.linux.dev,
linux-fsdevel@vger.kernel.org,
open list <linux-kernel@vger.kernel.org>,
lkft-triage@lists.linaro.org, Jeff Layton <jlayton@kernel.org>,
Dan Carpenter <dan.carpenter@linaro.org>,
Anders Roxell <anders.roxell@linaro.org>,
Arnd Bergmann <arnd@arndb.de>
Subject: Re: fs/netfs/read_retry.c:235:20: error: variable 'subreq' is uninitialized when used here [-Werror,-Wuninitialized]
Date: Tue, 03 Dec 2024 16:55:55 +0000 [thread overview]
Message-ID: <589335.1733244955@warthog.procyon.org.uk> (raw)
In-Reply-To: <CA+G9fYuLXDh8GDmgdhmA1NAhsma3=FoH1n93gmkHAGGFKbNGeQ@mail.gmail.com>
Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> Build error:
> ---------
> fs/netfs/read_retry.c:235:20: error: variable 'subreq' is
> uninitialized when used here [-Werror,-Wuninitialized]
> 235 | if (list_is_last(&subreq->rreq_link, &stream->subrequests))
> | ^~~~~~
> fs/netfs/read_retry.c:28:36: note: initialize the variable 'subreq' to
> silence this warning
> 28 | struct netfs_io_subrequest *subreq;
> | ^
> | = NULL
> 1 error generated.
> make[5]: *** [scripts/Makefile.build:194: fs/netfs/read_retry.o] Error 1
>
> Build image:
> -----------
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241126/testrun/26060810/suite/build/test/clang-19-lkftconfig/log
> - https://qa-reports.linaro.org/lkft/linux-next-master/build/next-20241126/testrun/26060810/suite/build/test/clang-19-lkftconfig/details/
> - https://storage.tuxsuite.com/public/linaro/lkft/builds/2pNKzjvChfT6aOWplZaZeQzbYCX/
>
> Steps to reproduce:
> ------------
> - tuxmake --runtime podman --target-arch x86_64 --toolchain clang-19
> --kconfig https://storage.tuxsuite.com/public/linaro/lkft/builds/2pNKzjvChfT6aOWplZaZeQzbYCX/config
> LLVM=1 LLVM_IAS=1
>
> The git log shows
> $ git log --oneline next-20241122..next-20241125 -- fs/netfs/read_retry.c
> 1bd9011ee163e netfs: Change the read result collector to only use one work item
> 5c962f9982cd9 netfs: Don't use bh spinlock
> 3c8a83f74e0ea netfs: Drop the was_async arg from netfs_read_subreq_terminated()
> 2029a747a14d2 netfs: Abstract out a rolling folio buffer implementation
>
> metadata:
> ----
> git describe: next-20241125 and next-20241126
> git repo: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> git sha: ed9a4ad6e5bd3a443e81446476718abebee47e82
> kernel config:
> https://storage.tuxsuite.com/public/linaro/lkft/builds/2pNKzjvChfT6aOWplZaZeQzbYCX/config
That should be fixed on my branch now:
https://git.kernel.org/pub/scm/linux/kernel/git/dhowells/linux-fs.git/log/?h=netfs-writeback
I'm just moving the branch to v6.13-rc1 and fixing reported issues before
asking Christian to repull it.
David
next prev parent reply other threads:[~2024-12-03 16:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-26 8:25 fs/netfs/read_retry.c:235:20: error: variable 'subreq' is uninitialized when used here [-Werror,-Wuninitialized] Naresh Kamboju
2024-11-26 8:49 ` Arnd Bergmann
2024-12-03 16:55 ` David Howells [this message]
2024-12-12 17:17 ` Nathan Chancellor
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=589335.1733244955@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=dan.carpenter@linaro.org \
--cc=jlayton@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkft-triage@lists.linaro.org \
--cc=naresh.kamboju@linaro.org \
--cc=netfs@lists.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