From: Tony Nguyen <anthony.l.nguyen@intel.com>
To: Li Zhong <floridsleeves@gmail.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<intel-wired-lan@lists.osuosl.org>
Cc: <pabeni@redhat.com>, <kuba@kernel.org>, <edumazet@google.com>,
<davem@davemloft.net>, <jesse.brandeburg@intel.com>
Subject: Re: [PATCH net-next v1] drivers/net/ethernet/intel/e100: check the return value of e100_exec_cmd()
Date: Mon, 12 Sep 2022 15:08:27 -0700 [thread overview]
Message-ID: <4ff0b209-2770-3790-ae93-3ea81c15a03e@intel.com> (raw)
In-Reply-To: <20220909041645.2612842-1-floridsleeves@gmail.com>
On 9/8/2022 9:16 PM, Li Zhong wrote:
> Check the return value of e100_exec_cmd() which could return error code
> when execution fails.
Are you coming across this as a real bug or as something reported by
static analysis? If the latter, I suggest checking the return value and
reporting it as debug, however, not changing existing behavior. We don't
have validation on this driver so there is limited ability to check for
regressions and the code has been like this for a long time without
reported issues.
Thanks,
Tony
> Signed-off-by: Li Zhong <floridsleeves@gmail.com>
> ---
> drivers/net/ethernet/intel/e100.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/intel/e100.c b/drivers/net/ethernet/intel/e100.c
> index 11a884aa5082..3b84745376fe 100644
> --- a/drivers/net/ethernet/intel/e100.c
> +++ b/drivers/net/ethernet/intel/e100.c
> @@ -1911,7 +1911,8 @@ static inline void e100_start_receiver(struct nic *nic, struct rx *rx)
>
> /* (Re)start RU if suspended or idle and RFA is non-NULL */
> if (rx->skb) {
> - e100_exec_cmd(nic, ruc_start, rx->dma_addr);
> + if (!e100_exec_cmd(nic, ruc_start, rx->dma_addr))
> + return;
> nic->ru_running = RU_RUNNING;
> }
> }
next prev parent reply other threads:[~2022-09-12 22:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 4:16 Li Zhong
2022-09-12 22:08 ` Tony Nguyen [this message]
2022-09-17 0:02 ` Li Zhong
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=4ff0b209-2770-3790-ae93-3ea81c15a03e@intel.com \
--to=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=floridsleeves@gmail.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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®