All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nick Desaulniers <ndesaulniers@google.com>
To: Nathan Chancellor <natechancellor@gmail.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	clang-built-linux@googlegroups.com
Subject: Re: [PATCH] iio: common: ssp_sensors: Initialize calculated_time in ssp_common_process_data
Date: Thu, 7 Mar 2019 16:35:26 -0800	[thread overview]
Message-ID: <CAKwvOdkeVmcoD7WusKE83MmRjX+h73rnHDY=Rn_a7LXsULPsrw@mail.gmail.com> (raw)
In-Reply-To: <20190307214546.9624-1-natechancellor@gmail.com>

On Thu, Mar 7, 2019 at 1:46 PM Nathan Chancellor
<natechancellor@gmail.com> wrote:
>
> When building with -Wsometimes-uninitialized, Clang warns:
>
> drivers/iio/common/ssp_sensors/ssp_iio.c:95:6: warning: variable
> 'calculated_time' is used uninitialized whenever 'if' condition is false
> [-Wsometimes-uninitialized]
>
> While it isn't wrong, this will never be a problem because
> iio_push_to_buffers_with_timestamp only uses calculated_time
> on the same condition that it is assigned (when scan_timestamp
> is not zero). While iio_push_to_buffers_with_timestamp is marked
> as inline, Clang does inlining in the optimization stage, which
> happens after the semantic analysis phase (plus inline is merely
> a hint to the compiler).
>
> Fix this by just zero initializing calculated_time.
>
> Link: https://github.com/ClangBuiltLinux/linux/issues/394
> Signed-off-by: Nathan Chancellor <natechancellor@gmail.com>

Knowing that the same invariant holds across function boundaries to
protect access of unitialized values and thus undefined behavior
sounds tricky to diagnose accurately.  Thanks for the patch.
Reviewed-by: Nick Desaulniers <ndesaulniers@google.com>

> ---
>  drivers/iio/common/ssp_sensors/ssp_iio.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/iio/common/ssp_sensors/ssp_iio.c b/drivers/iio/common/ssp_sensors/ssp_iio.c
> index 645f2e3975db..e38f704d88b7 100644
> --- a/drivers/iio/common/ssp_sensors/ssp_iio.c
> +++ b/drivers/iio/common/ssp_sensors/ssp_iio.c
> @@ -81,7 +81,7 @@ int ssp_common_process_data(struct iio_dev *indio_dev, void *buf,
>                             unsigned int len, int64_t timestamp)
>  {
>         __le32 time;
> -       int64_t calculated_time;
> +       int64_t calculated_time = 0;
>         struct ssp_sensor_data *spd = iio_priv(indio_dev);
>
>         if (indio_dev->scan_bytes == 0)
> --
> 2.21.0
>


-- 
Thanks,
~Nick Desaulniers

  reply	other threads:[~2019-03-08  0:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07 21:45 [PATCH] iio: common: ssp_sensors: Initialize calculated_time in ssp_common_process_data Nathan Chancellor
2019-03-08  0:35 ` Nick Desaulniers [this message]
2019-03-10  9:37   ` Jonathan Cameron
2019-03-11 11:10     ` Arnd Bergmann
2019-03-11 13:50       ` 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='CAKwvOdkeVmcoD7WusKE83MmRjX+h73rnHDY=Rn_a7LXsULPsrw@mail.gmail.com' \
    --to=ndesaulniers@google.com \
    --cc=clang-built-linux@googlegroups.com \
    --cc=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=natechancellor@gmail.com \
    --cc=pmeerw@pmeerw.net \
    /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.