From: "Saleem, Shiraz" <shiraz.saleem@intel.com>
To: coverity-bot <keescook@chromium.org>,
"Ismail, Mustafa" <mustafa.ismail@intel.com>,
"Nikolova, Tatyana E" <tatyana.e.nikolova@intel.com>
Cc: "Gustavo A. R. Silva" <gustavoars@kernel.org>,
Jason Gunthorpe <jgg@nvidia.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: RE: Coverity: irdma_fill_device_info(): Null pointer dereferences
Date: Tue, 15 Jun 2021 15:58:52 +0000 [thread overview]
Message-ID: <6bdaf0a1b0e74782b63afba1ecbdd348@intel.com> (raw)
In-Reply-To: <202106081056.E270F59@keescook>
> 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.
This vsi object is obtained from the PCI driver's [ice] PF object.
And this pf->vsi is setup in ice_probe and always valid by the time this function
is called from irdma_probe.
> 230 rf->default_vsi.vsi_idx = vsi->vsi_num;
> 231 rf->protocol_used = IRDMA_ROCE_PROTOCOL_ONLY;
> 232 rf->rdma_ver = IRDMA_GEN_2;
> 233 rf->rsrc_profile = IRDMA_HMC_PROFILE_DEFAULT;
> 234 rf->rst_to = IRDMA_RST_TIMEOUT_HZ;
> 235 rf->gen_ops.request_reset = irdma_request_reset;
>
> If this is a false positive, please let us know so we can mark it as such, or teach
> the Coverity rules to be smarter. If not, please make sure fixes get into linux-next.
> :) For patches fixing this, please include these lines (but double-check the "Fixes"
> first):
>
> Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
> Addresses-Coverity-ID: 1505164 ("Null pointer dereferences")
> Fixes: 8498a30e1b94 ("RDMA/irdma: Register auxiliary driver and implement
> private channel OPs")
>
> Thanks for your attention!
>
> --
> Coverity-bot
next prev parent reply other threads:[~2021-06-15 16:00 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 [this message]
2021-06-15 16:01 ` Jason Gunthorpe
2021-06-17 14:18 ` Saleem, Shiraz
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=6bdaf0a1b0e74782b63afba1ecbdd348@intel.com \
--to=shiraz.saleem@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 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).