From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: "Chen, Rong A" <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
Alviro Iskandar Setiawan <[email protected]>,
io-uring Mailing list <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Dan Carpenter <[email protected]>,
Pavel Begunkov <[email protected]>,
Tea Inside Mailing List <[email protected]>,
kernel test robot <[email protected]>
Subject: Re: [PATCH io_uring-5.17 v2] io_uring: Clean up a false-positive warning from GCC 9.3.0
Date: Mon, 07 Feb 2022 08:38:22 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
On Mon, 7 Feb 2022 21:05:33 +0700, Ammar Faizi wrote:
> From: Alviro Iskandar Setiawan <[email protected]>
>
> In io_recv(), if import_single_range() fails, the @flags variable is
> uninitialized, then it will goto out_free.
>
> After the goto, the compiler doesn't know that (ret < min_ret) is
> always true, so it thinks the "if ((flags & MSG_WAITALL) ..." path
> could be taken.
>
> [...]
Applied, thanks!
[1/1] io_uring: Clean up a false-positive warning from GCC 9.3.0
commit: 0d7c1153d9291197c1dc473cfaade77acb874b4b
Best regards,
--
Jens Axboe
next prev parent reply other threads:[~2022-02-07 15:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <61f5a2fa./zZ+BkSwdkmvxv7x%[email protected]>
2022-01-30 9:11 ` [ammarfaizi2-block:testing/io_uring-sendto-recvfrom.v1] BUILD SUCCESS 68d110c39241b887ec388cd3316dbedb85b0cbcf Ammar Faizi
2022-02-07 6:13 ` Chen, Rong A
2022-02-07 11:43 ` [PATCH io_uring-5.17] io_uring: Fix build error potential reading uninitialized value Ammar Faizi
2022-02-07 13:45 ` Jens Axboe
2022-02-07 14:05 ` [PATCH io_uring-5.17 v2] io_uring: Clean up a false-positive warning from GCC 9.3.0 Ammar Faizi
2022-02-07 15:38 ` Jens Axboe [this message]
2022-02-07 14:20 ` [PATCH io_uring-5.17] io_uring: Fix build error potential reading uninitialized value Dan Carpenter
2022-02-07 14:33 ` Alviro Iskandar Setiawan
2022-02-07 15:37 ` Jens Axboe
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=164424830208.19639.16912208440698766253.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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