From: Dan Carpenter <dan.carpenter@linaro.org>
To: Gregory Greenman <gregory.greenman@intel.com>
Cc: Kalle Valo <kvalo@kernel.org>,
Johannes Berg <johannes.berg@intel.com>,
Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Shaul Triebitz <shaul.triebitz@intel.com>,
linux-wireless@vger.kernel.org, kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] wifi: iwlwifi: mvm: fix an error code in iwl_mvm_mld_add_sta()
Date: Thu, 26 Oct 2023 13:42:00 +0300 [thread overview]
Message-ID: <79f70bb6-ca33-48fc-ab33-6a6cd8ba2e1d@kadam.mountain> (raw)
In-Reply-To: <75e4ea09-db58-462f-bd4e-5ad4e5e5dcb5@moroto.mountain>
Ping?
regards,
dan carpenter
On Wed, Sep 27, 2023 at 03:40:41PM +0300, Dan Carpenter wrote:
> This error path should return -EINVAL instead of success.
>
> Fixes: 57974a55d995 ("wifi: iwlwifi: mvm: refactor iwl_mvm_mac_sta_state_common()")
> Signed-off-by: Dan Carpenter <dan.carpenter@linaro.org>
> ---
> I copy and pasted this approach from similar code in the same patch.
>
> drivers/net/wireless/intel/iwlwifi/mvm/mld-sta.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/mld-sta.c b/drivers/net/wireless/intel/iwlwifi/mvm/mld-sta.c
> index 1464aad039e1..f2e952481ff8 100644
> --- a/drivers/net/wireless/intel/iwlwifi/mvm/mld-sta.c
> +++ b/drivers/net/wireless/intel/iwlwifi/mvm/mld-sta.c
> @@ -707,8 +707,10 @@ int iwl_mvm_mld_add_sta(struct iwl_mvm *mvm, struct ieee80211_vif *vif,
> rcu_dereference_protected(mvm_sta->link[link_id],
> lockdep_is_held(&mvm->mutex));
>
> - if (WARN_ON(!link_conf || !mvm_link_sta))
> + if (WARN_ON(!link_conf || !mvm_link_sta)) {
> + ret = -EINVAL;
> goto err;
> + }
>
> ret = iwl_mvm_mld_cfg_sta(mvm, sta, vif, link_sta, link_conf,
> mvm_link_sta);
> --
> 2.39.2
next prev parent reply other threads:[~2023-10-26 10:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 12:40 [PATCH] wifi: iwlwifi: mvm: fix an error code in iwl_mvm_mld_add_sta() Dan Carpenter
2023-10-26 10:42 ` Dan Carpenter [this message]
2023-10-26 10:44 ` Korenblit, Miriam Rachel
2023-10-26 14:09 ` Greenman, Gregory
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=79f70bb6-ca33-48fc-ab33-6a6cd8ba2e1d@kadam.mountain \
--to=dan.carpenter@linaro.org \
--cc=gregory.greenman@intel.com \
--cc=johannes.berg@intel.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=shaul.triebitz@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