From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: mingli yu <mingli.yu@windriver.com>
Cc: lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: [babeltrace][PATCH] fs.c: initialize the other_entry variable
Date: Wed, 11 Mar 2020 09:58:06 -0400 (EDT) [thread overview]
Message-ID: <1707083610.24791.1583935086375.JavaMail.zimbra@efficios.com> (raw)
In-Reply-To: <1583933970-68840-1-git-send-email-mingli.yu@windriver.com>
----- On Mar 11, 2020, at 9:39 AM, mingli yu mingli.yu@windriver.com wrote:
> From: Mingli Yu <mingli.yu@windriver.com>
>
> Initialize the pointer other_entry to fix the below error:
>| ../../../../../git/src/plugins/ctf/fs-src/fs.c: In function
>| 'ds_index_insert_ds_index_entry_sorted':
>| ../../../../../git/src/plugins/ctf/fs-src/fs.c:702:5: error: 'other_entry' may
>| be used uninitialized in this function [-Werror=maybe-uninitialized]
>| 702 | !ds_index_entries_equal(entry, other_entry)) {
It would be good that the commit message documents that the purpose of this
change is only to silence compiler warnings (which is indeed a good thing to
do).
It does not seem to ever be possible to reach a situation where the
uninitialized value is used, because the only case which can leave
this variable uninitialized is if index->entries->len == 0, which means
the "if (i == index->entries->len ||" will be taken (true), which will
therefore skip the second sub-expression of the if:
"!ds_index_entries_equal(entry, other_entry)", which is the only place
where "other_entry" is read.
Thanks,
Mathieu
>
> Signed-off-by: Mingli Yu <mingli.yu@windriver.com>
> ---
> src/plugins/ctf/fs-src/fs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/src/plugins/ctf/fs-src/fs.c b/src/plugins/ctf/fs-src/fs.c
> index e87523a..a6b5315 100644
> --- a/src/plugins/ctf/fs-src/fs.c
> +++ b/src/plugins/ctf/fs-src/fs.c
> @@ -680,7 +680,7 @@ void ds_index_insert_ds_index_entry_sorted(
> struct ctf_fs_ds_index_entry *entry)
> {
> guint i;
> - struct ctf_fs_ds_index_entry *other_entry;
> + struct ctf_fs_ds_index_entry *other_entry = NULL;
>
> /* Find the spot where to insert this index entry. */
> for (i = 0; i < index->entries->len; i++) {
> --
> 2.7.4
>
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev
--
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com
next prev parent reply other threads:[~2020-03-11 13:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 13:39 [babeltrace][PATCH] fs.c: initialize the other_entry variable mingli.yu
2020-03-11 13:52 ` Simon Marchi
2020-03-12 3:37 ` Yu, Mingli via lttng-dev
2020-03-11 13:58 ` Mathieu Desnoyers [this message]
2020-03-12 3:42 ` [babeltrace][PATCH v2] " mingli.yu--- via lttng-dev
-- strict thread matches above, loose matches on Subject: below --
2020-03-11 13:25 [babeltrace][PATCH] " mingli.yu
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=1707083610.24791.1583935086375.JavaMail.zimbra@efficios.com \
--to=mathieu.desnoyers@efficios.com \
--cc=lttng-dev@lists.lttng.org \
--cc=mingli.yu@windriver.com \
/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;
as well as URLs for NNTP newsgroup(s).