From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Rouven Czerwinski <r.czerwinski@pengutronix.de>,
barebox@lists.infradead.org
Subject: Re: [PATCH] include: linux/iopoll: fix uninitialized warning
Date: Tue, 10 Sep 2024 10:25:56 +0200 [thread overview]
Message-ID: <909c7ab9-0f7f-4d50-9a80-2c9026272cc8@pengutronix.de> (raw)
In-Reply-To: <20240903093712.453901-1-r.czerwinski@pengutronix.de>
Hello Rouven,
On 03.09.24 11:37, Rouven Czerwinski wrote:
> In gcc 13.3 there is a warning that start may be used unitialized:
>
> include/linux/iopoll.h:42:21: warning: ‘start’ may be used uninitialized [-Wmaybe-uninitialized]
> 42 | is_timeout(start, ((timeout_us) * USECOND))) { \
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> The warning is bogus since before usage of start !IN_PBL and
> timeout_us != 0 are checked for the case where start is used, but in
> this case it is also always initialized to get_time_ns().
> Initialize it to zero to silence the warning.
FTR: Here's the GCC bugzilla report about this false positive:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98049
Thanks for the workaround,
Ahmad
>
> Signed-off-by: Rouven Czerwinski <r.czerwinski@pengutronix.de>
> ---
> include/linux/iopoll.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/include/linux/iopoll.h b/include/linux/iopoll.h
> index 96b17dee48..c7dcaec382 100644
> --- a/include/linux/iopoll.h
> +++ b/include/linux/iopoll.h
> @@ -31,7 +31,7 @@
> */
> #define read_poll_timeout(op, val, cond, timeout_us, args...) \
> ({ \
> - uint64_t start; \
> + uint64_t start = 0; \
> if (!IN_PBL && (timeout_us) != 0) \
> start = get_time_ns(); \
> for (;;) { \
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2024-09-10 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 9:37 Rouven Czerwinski
2024-09-03 11:39 ` Sascha Hauer
2024-09-10 8:25 ` Ahmad Fatoum [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=909c7ab9-0f7f-4d50-9a80-2c9026272cc8@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=r.czerwinski@pengutronix.de \
/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