From: Stanislaw Gruszka <stf_xl@wp.pl>
To: Wentao Liang <vulab@iscas.ac.cn>
Cc: kvalo@kernel.org, linux-wireless@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iwlegacy/4965: Cancel deferred work on device init failure
Date: Tue, 4 Mar 2025 17:44:07 +0100 [thread overview]
Message-ID: <20250304164407.GB67578@wp.pl> (raw)
In-Reply-To: <20250304031603.1989-1-vulab@iscas.ac.cn>
Hi
On Tue, Mar 04, 2025 at 11:16:03AM +0800, Wentao Liang wrote:
> In __il4965_up(), deferred work is not canceled in time when device
> initialization fails. This is harmless if the device has not started.
> However, in il4965_bg_restart(), if the device remains operational
> in any state other than S_FW_ERROR or S_EXIT_PENDING, a dereference
> operation needs to be performed when __il4965_up() fails.
>
> Add il4965_cancel_deferred_work() to the failure path of
> __il4965_up() to prevent potential errors. Even if the current code
> does not exhibit the described issues, adding this change can prevent
> future problems at minimal cost, improving the robustness of the code.
I think preventing potential future problems in this legacy driver
is not necessary since the driver will not be developed further.
> Signed-off-by: Wentao Liang <vulab@iscas.ac.cn>
> ---
> drivers/net/wireless/intel/iwlegacy/4965-mac.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/wireless/intel/iwlegacy/4965-mac.c b/drivers/net/wireless/intel/iwlegacy/4965-mac.c
> index 05c4af41bdb9..3b21bd79f3a9 100644
> --- a/drivers/net/wireless/intel/iwlegacy/4965-mac.c
> +++ b/drivers/net/wireless/intel/iwlegacy/4965-mac.c
> @@ -5591,6 +5591,8 @@ __il4965_up(struct il_priv *il)
> __il4965_down(il);
> clear_bit(S_EXIT_PENDING, &il->status);
>
> + il4965_cancel_deferred_work(il);
We can not cancel here as we have il->mutex locked, it will
deadlock in case of some pending work that holds the mutex.
> /* tried to restart and config the device for as long as our
> * patience could withstand */
> IL_ERR("Unable to initialize device after %d attempts.\n", i);
> --
> 2.42.0.windows.2
>
prev parent reply other threads:[~2025-03-04 16:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-04 3:16 [PATCH] iwlegacy/4965: Cancel deferred work on device init failure Wentao Liang
2025-03-04 16:44 ` Stanislaw Gruszka [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=20250304164407.GB67578@wp.pl \
--to=stf_xl@wp.pl \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=vulab@iscas.ac.cn \
/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