From: Ajit Khaparde <ajit.khaparde@broadcom.com>
To: Kalesh A P <kalesh-anakkur.purayil@broadcom.com>
Cc: dpdk-dev <dev@dpdk.org>, Ferruh Yigit <ferruh.yigit@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/bnxt: fix unchecked return value
Date: Wed, 17 Mar 2021 17:44:22 -0700 [thread overview]
Message-ID: <CACZ4nhtY1xqa+aCwYs2oksfx8M3zRh7DzgWP7L3qL_hXM=nrdQ@mail.gmail.com> (raw)
In-Reply-To: <20210316054125.980-1-kalesh-anakkur.purayil@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 1840 bytes --]
On Mon, Mar 15, 2021 at 10:19 PM Kalesh A P
<kalesh-anakkur.purayil@broadcom.com> wrote:
>
> From: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
>
> CID 363716 (#1 of 1): Unchecked return value (CHECKED_RETURN)
> check_return: Calling rte_pci_write_config without checking
> return value (as is done elsewhere 46 out of 49 times).
>
> Coverity issue: 363716
>
> Fixes: be14720def9c ("net/bnxt: support FW reset")
> Cc: stable@dpdk.org
>
> Signed-off-by: Kalesh AP <kalesh-anakkur.purayil@broadcom.com>
> Reviewed-by: Somnath Kotur <somnath.kotur@broadcom.com>
Patch applied to dpdk-next-net-brcm.
> ---
> drivers/net/bnxt/bnxt_ethdev.c | 8 +++++++-
> 1 file changed, 7 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/bnxt/bnxt_ethdev.c b/drivers/net/bnxt/bnxt_ethdev.c
> index 6cc6af0..202b082 100644
> --- a/drivers/net/bnxt/bnxt_ethdev.c
> +++ b/drivers/net/bnxt/bnxt_ethdev.c
> @@ -3860,13 +3860,19 @@ static void bnxt_write_fw_reset_reg(struct bnxt *bp, uint32_t index)
> uint32_t val = info->reset_reg_val[index];
> uint32_t reg = info->reset_reg[index];
> uint32_t type, offset;
> + int ret;
>
> type = BNXT_FW_STATUS_REG_TYPE(reg);
> offset = BNXT_FW_STATUS_REG_OFF(reg);
>
> switch (type) {
> case BNXT_FW_STATUS_REG_TYPE_CFG:
> - rte_pci_write_config(bp->pdev, &val, sizeof(val), offset);
> + ret = rte_pci_write_config(bp->pdev, &val, sizeof(val), offset);
> + if (ret < 0) {
> + PMD_DRV_LOG(ERR, "Failed to write %#x at PCI offset %#x",
> + val, offset);
> + return;
> + }
> break;
> case BNXT_FW_STATUS_REG_TYPE_GRC:
> offset = bnxt_map_reset_regs(bp, offset);
> --
> 2.10.1
>
prev parent reply other threads:[~2021-03-18 0:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-16 5:41 Kalesh A P
2021-03-18 0:44 ` Ajit Khaparde [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='CACZ4nhtY1xqa+aCwYs2oksfx8M3zRh7DzgWP7L3qL_hXM=nrdQ@mail.gmail.com' \
--to=ajit.khaparde@broadcom.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=kalesh-anakkur.purayil@broadcom.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).