From: Jens Axboe <axboe@kernel.dk>
To: Ammar Faizi <ammarfaizi2@gnuweeb.org>
Cc: "Chen, Rong A" <rong.a.chen@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alviro Iskandar Setiawan <alviro.iskandar@gmail.com>,
io-uring Mailing list <io-uring@vger.kernel.org>,
GNU/Weeb Mailing List <gwml@gnuweeb.org>,
Dan Carpenter <dan.carpenter@oracle.com>,
Pavel Begunkov <asml.silence@gmail.com>,
Tea Inside Mailing List <timl@vger.teainside.org>,
kernel test robot <lkp@intel.com>
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: <164424830208.19639.16912208440698766253.b4-ty@kernel.dk> (raw)
In-Reply-To: <20220207140533.565411-1-ammarfaizi2@gnuweeb.org>
On Mon, 7 Feb 2022 21:05:33 +0700, Ammar Faizi wrote:
> From: Alviro Iskandar Setiawan <alviro.iskandar@gmail.com>
>
> 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:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d33bb5a9-8173-f65b-f653-51fc0681c6d6@intel.com>
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 \
--to=axboe@kernel.dk \
--cc=alviro.iskandar@gmail.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=asml.silence@gmail.com \
--cc=dan.carpenter@oracle.com \
--cc=gwml@gnuweeb.org \
--cc=io-uring@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=rong.a.chen@intel.com \
--cc=timl@vger.teainside.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 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.