From: David Miller <davem@davemloft.net>
To: colin.king@canonical.com
Cc: peppe.cavallaro@st.com, alexandre.torgue@st.com,
joabreu@synopsys.com, mcoquelin.stm32@gmail.com,
netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com,
linux-arm-kernel@lists.infradead.org,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] net: stmmac: add sanity check to device_property_read_u32_array call
Date: Tue, 18 Jun 2019 21:04:30 -0400 (EDT) [thread overview]
Message-ID: <20190618.210430.1199248693691754077.davem@davemloft.net> (raw)
In-Reply-To: <20190617165836.4673-1-colin.king@canonical.com>
From: Colin King <colin.king@canonical.com>
Date: Mon, 17 Jun 2019 17:58:36 +0100
> From: Colin Ian King <colin.king@canonical.com>
>
> Currently the call to device_property_read_u32_array is not error checked
> leading to potential garbage values in the delays array that are then used
> in msleep delays. Add a sanity check to the property fetching.
>
> Addresses-Coverity: ("Uninitialized scalar variable")
> Signed-off-by: Colin Ian King <colin.king@canonical.com>
Applied to net-next, thanks Colin.
Please make the destination tree explicit in the future by putting
something like "[PATCH net-next]" in the Subject line.
Thank you.
next prev parent reply other threads:[~2019-06-19 1:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 16:58 Colin King
2019-06-19 1:04 ` David Miller [this message]
2019-06-19 5:13 ` Martin Blumenstingl
2019-06-19 6:55 ` Colin Ian King
2019-06-20 1:34 ` Martin Blumenstingl
2019-06-25 4:44 ` Martin Blumenstingl
2019-06-25 7:58 ` Colin Ian King
2019-06-28 4:15 ` Martin Blumenstingl
2019-06-28 8:32 ` Colin Ian King
2019-06-28 16:05 ` Martin Blumenstingl
2019-07-01 22:43 ` Martin Blumenstingl
2019-07-02 6:48 ` Colin Ian King
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=20190618.210430.1199248693691754077.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexandre.torgue@st.com \
--cc=colin.king@canonical.com \
--cc=joabreu@synopsys.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=peppe.cavallaro@st.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
all inboxes | Powered by JetHome®