From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: Jason Gunthorpe <jgg@nvidia.com>
Cc: coverity-bot <keescook@chromium.org>,
"Ismail, Mustafa" <mustafa.ismail@intel.com>,
"Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>,
"Gustavo A. R. Silva" <gustavoars@kernel.org>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>
Subject: RE: Coverity: irdma_fill_device_info(): Null pointer dereferences
Date: Thu, 17 Jun 2021 14:18:19 +0000 [thread overview]
Message-ID: <7c693feb84ce452ab2a7ad8f77720194@intel.com> (raw)
In-Reply-To: <20210615160159.GV1002214@nvidia.com>
> Subject: Re: Coverity: irdma_fill_device_info(): Null pointer dereferences
>
> On Tue, Jun 15, 2021 at 03:58:52PM +0000, Saleem, Shiraz wrote:
> > > Subject: Coverity: irdma_fill_device_info(): Null pointer
> > > dereferences
> > >
> > > Hello!
> > >
> > > This is an experimental semi-automated report about issues detected
> > > by Coverity from a scan of next-20210608 as part of the linux-next scan
> project:
> > > https://scan.coverity.com/projects/linux-next-weekly-scan
> > >
> > > You're getting this email because you were associated with the
> > > identified lines of code (noted below) that were touched by commits:
> > >
> > > Wed Jun 2 19:55:16 2021 -0300
> > > 8498a30e1b94 ("RDMA/irdma: Register auxiliary driver and
> > > implement private channel OPs")
> > >
> > > Coverity reported the following:
> > >
> > > *** CID 1505164: Null pointer dereferences (NULL_RETURNS)
> > > /drivers/infiniband/hw/irdma/main.c: 230 in irdma_fill_device_info()
> > > 224 rf->gen_ops.register_qset = irdma_lan_register_qset;
> > > 225 rf->gen_ops.unregister_qset = irdma_lan_unregister_qset;
> > > 226 rf->hw.hw_addr = pf->hw.hw_addr;
> > > 227 rf->pcidev = pf->pdev;
> > > 228 rf->msix_count = pf->num_rdma_msix;
> > > 229 rf->msix_entries = &pf->msix_entries[pf->rdma_base_vector];
> > > vvv CID 1505164: Null pointer dereferences (NULL_RETURNS)
> > > vvv Dereferencing "vsi", which is known to be "NULL".
> >
> > This is a false +ve IMO.
>
> It is because of this:
>
> static inline struct ice_vsi *ice_get_main_vsi(struct ice_pf *pf) {
> if (pf->vsi)
> return pf->vsi[0];
>
> return NULL;
> }
>
> If the above can't return null it should be rewritten
It does appear on review that the pf->vsi can really never be NULL for paths that call ice_get_main_vsi.
We are running some tests to confirm there is no fallout. And if so, we can just return pf->vsi[0]
as a fix.
Shiraz
prev parent reply other threads:[~2021-06-17 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 17:56 Coverity: irdma_fill_device_info(): Null pointer dereferences coverity-bot
2021-06-15 15:58 ` Saleem, Shiraz
2021-06-15 16:01 ` Jason Gunthorpe
2021-06-17 14:18 ` Saleem, Shiraz [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=7c693feb84ce452ab2a7ad8f77720194@intel.com \
--to=shiraz.saleem@intel.com \
--cc=anthony.l.nguyen@intel.com \
--cc=gustavo@embeddedor.com \
--cc=gustavoars@kernel.org \
--cc=jgg@nvidia.com \
--cc=keescook@chromium.org \
--cc=linux-next@vger.kernel.org \
--cc=mustafa.ismail@intel.com \
--cc=tatyana.e.nikolova@intel.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 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.