From: Saeed Mahameed <saeedm@nvidia.com>
To: "tim.gardner@canonical.com" <tim.gardner@canonical.com>,
Vlad Buslov <vladbu@nvidia.com>
Cc: "linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
Roi Dayan <roid@nvidia.com>,
"vladimir.oltean@nxp.com" <vladimir.oltean@nxp.com>,
Mark Bloch <mbloch@nvidia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"kuba@kernel.org" <kuba@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"leon@kernel.org" <leon@kernel.org>,
Jianbo Liu <jianbol@nvidia.com>
Subject: Re: [PATCH][linux-next] net/mlx5: Bridge, fix uninitialized variable in mlx5_esw_bridge_port_changeupper()
Date: Thu, 19 Aug 2021 07:50:51 +0000 [thread overview]
Message-ID: <f42ff8df9d10b6e171e3ca45247a3df9b9fba71c.camel@nvidia.com> (raw)
In-Reply-To: <ygnh8s0ypumc.fsf@nvidia.com>
On Wed, 2021-08-18 at 19:47 +0300, Vlad Buslov wrote:
> On Wed 18 Aug 2021 at 18:52, Tim Gardner <tim.gardner@canonical.com>
> wrote:
> > A recent change removed code that initialized the return code
> > variable 'err'. It
> > is now possible for mlx5_esw_bridge_port_changeupper() to return an
> > error code
> > using this uninitialized variable. Fix it by initializing to 0.
> >
> > Addresses-Coverity: ("Uninitialized scalar variable (UNINIT)")
> >
> > Cc: Saeed Mahameed <saeedm@nvidia.com>
> > Cc: Leon Romanovsky <leon@kernel.org>
> > Cc: "David S. Miller" <davem@davemloft.net>
> > Cc: Jakub Kicinski <kuba@kernel.org>
> > Cc: Vlad Buslov <vladbu@nvidia.com>
> > Cc: Jianbo Liu <jianbol@nvidia.com>
> > Cc: Mark Bloch <mbloch@nvidia.com>
> > Cc: Roi Dayan <roid@nvidia.com>
> > Cc: Vladimir Oltean <vladimir.oltean@nxp.com>
> > Cc: netdev@vger.kernel.org
> > Cc: linux-rdma@vger.kernel.org
> > Cc: linux-kernel@vger.kernel.org
Just wondering, do we really need 12 inline CCs for fixing a poor
coverity?
> > Signed-off-by: Tim Gardner <tim.gardner@canonical.com>
> > ---
>
> Tim, thanks for fixing this!
>
> Saeed, this is the second similar issue that I mentioned in my reply
> to
> Colin. Again, I've already submitted same patch internally and this
> one
> is as good as mine.
I don't mind both patches are perfect.
>
> Reviewed-by: Vlad Buslov <vladbu@nvidia.com>
>
> [...]
>
>
prev parent reply other threads:[~2021-08-19 7:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-18 15:52 [PATCH][linux-next] net/mlx5: Bridge, fix uninitialized variable in mlx5_esw_bridge_port_changeupper() Tim Gardner
2021-08-18 16:47 ` Vlad Buslov
2021-08-19 7:50 ` Saeed Mahameed [this message]
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=f42ff8df9d10b6e171e3ca45247a3df9b9fba71c.camel@nvidia.com \
--to=saeedm@nvidia.com \
--cc=davem@davemloft.net \
--cc=jianbol@nvidia.com \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=roid@nvidia.com \
--cc=tim.gardner@canonical.com \
--cc=vladbu@nvidia.com \
--cc=vladimir.oltean@nxp.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).