From: Jakub Kicinski <kuba@kernel.org>
To: Michael Chan <michael.chan@broadcom.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
pabeni@redhat.com, gospo@broadcom.com,
Kalesh AP <kalesh-anakkur.purayil@broadcom.com>,
Vikas Gupta <vikas.gupta@broadcom.com>,
Somnath Kotur <somnath.kotur@broadcom.com>
Subject: Re: [PATCH net v2 3/4] bnxt_en: Fix wrong return value check in bnxt_close_nic()
Date: Thu, 7 Dec 2023 14:31:02 -0800 [thread overview]
Message-ID: <20231207143102.049820a2@kernel.org> (raw)
In-Reply-To: <CACKFLi=ZV42LZqAC6_cWtLfwURyzd6DW9-BQddbozkBSfr31kg@mail.gmail.com>
On Thu, 7 Dec 2023 14:24:24 -0800 Michael Chan wrote:
> The code will always proceed to do the close when
> wait_event_interruptible_timeout() returns for any reason. The check
> is just to log a warning message that the wait has timed out and we're
> closing anyway.
>
> What I can do is to log another warning if the wait is interrupted by
> a signal. Since we do the close no matter what, the error code should
> not be returned to the caller and the function should be changed to
> void. Does that sound reasonable?
Yup!
next prev parent reply other threads:[~2023-12-07 22:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 0:05 [PATCH net v2 0/4] bnxt_en: Misc. fixes Michael Chan
2023-12-07 0:05 ` [PATCH net v2 1/4] bnxt_en: Clear resource reservation during resume Michael Chan
2023-12-07 18:20 ` Jakub Kicinski
2023-12-07 0:05 ` [PATCH net v2 2/4] bnxt_en: Fix skb recycling logic in bnxt_deliver_skb() Michael Chan
2023-12-07 18:21 ` Jakub Kicinski
2023-12-07 18:22 ` Jakub Kicinski
2023-12-07 18:37 ` Andy Gospodarek
2023-12-07 18:41 ` Jakub Kicinski
2023-12-07 0:05 ` [PATCH net v2 3/4] bnxt_en: Fix wrong return value check in bnxt_close_nic() Michael Chan
2023-12-07 18:27 ` Jakub Kicinski
2023-12-07 22:24 ` Michael Chan
2023-12-07 22:31 ` Jakub Kicinski [this message]
2023-12-07 0:05 ` [PATCH net v2 4/4] bnxt_en: Fix HWTSTAMP_FILTER_ALL packet timestamp logic Michael Chan
2023-12-07 12:04 ` [PATCH net v2 0/4] bnxt_en: Misc. fixes Vadim Fedorenko
2023-12-07 16:24 ` Michael Chan
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=20231207143102.049820a2@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gospo@broadcom.com \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=somnath.kotur@broadcom.com \
--cc=vikas.gupta@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).