From: Johannes Berg <johannes@sipsolutions.net>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: Wey-Yi Guy <wey-yi.w.guy@intel.com>,
Intel Linux Wireless <ilw@linux.intel.com>,
linux-wireless@vger.kernel.org
Subject: Re: [PATCH] iwlwifi: do not nulify ctx->vif on reset
Date: Tue, 13 Mar 2012 16:15:30 +0100 [thread overview]
Message-ID: <1331651730.3329.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1331651434-4370-1-git-send-email-sgruszka@redhat.com> (sfid-20120313_161044_513721_26122C7B)
On Tue, 2012-03-13 at 16:10 +0100, Stanislaw Gruszka wrote:
> ctx->vif is dereferenced in different part of iwlwifi code, so do not
> nullify it.
>
> This should address at least one of the possible reasons of WARNING at
> iwlagn_mac_remove_interface, and perhaps some random crashes when
> firmware reset is performed.
I'm not completely convinced -- there are parts of the driver that are
active even when no interface has ever been added.
Have you seen crashes due to this? I have seen the warning in the past
but in some recent firmware reset testing I never ran into it again...
johannes
> Cc: stable@vger.kernel.org
> Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
> ---
> drivers/net/wireless/iwlwifi/iwl-agn.c | 3 ---
> drivers/net/wireless/iwlwifi/iwl-mac80211.c | 10 +++++++++-
> 2 files changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/wireless/iwlwifi/iwl-agn.c b/drivers/net/wireless/iwlwifi/iwl-agn.c
> index 28422c0..6375e5a 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-agn.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-agn.c
> @@ -862,7 +862,6 @@ static void iwl_bg_run_time_calib_work(struct work_struct *work)
>
> void iwlagn_prepare_restart(struct iwl_priv *priv)
> {
> - struct iwl_rxon_context *ctx;
> bool bt_full_concurrent;
> u8 bt_ci_compliance;
> u8 bt_load;
> @@ -871,8 +870,6 @@ void iwlagn_prepare_restart(struct iwl_priv *priv)
>
> lockdep_assert_held(&priv->mutex);
>
> - for_each_context(priv, ctx)
> - ctx->vif = NULL;
> priv->is_open = 0;
>
> /*
> diff --git a/drivers/net/wireless/iwlwifi/iwl-mac80211.c b/drivers/net/wireless/iwlwifi/iwl-mac80211.c
> index 9212ee3..4e8786d 100644
> --- a/drivers/net/wireless/iwlwifi/iwl-mac80211.c
> +++ b/drivers/net/wireless/iwlwifi/iwl-mac80211.c
> @@ -1241,6 +1241,7 @@ static int iwlagn_mac_add_interface(struct ieee80211_hw *hw,
> struct iwl_rxon_context *tmp, *ctx = NULL;
> int err;
> enum nl80211_iftype viftype = ieee80211_vif_type_p2p(vif);
> + bool reset = false;
>
> IWL_DEBUG_MAC80211(priv, "enter: type %d, addr %pM\n",
> viftype, vif->addr);
> @@ -1262,6 +1263,13 @@ static int iwlagn_mac_add_interface(struct ieee80211_hw *hw,
> tmp->interface_modes | tmp->exclusive_interface_modes;
>
> if (tmp->vif) {
> + /* On reset we need to add the same interface again */
> + if (tmp->vif == vif) {
> + reset = true;
> + ctx = tmp;
> + break;
> + }
> +
> /* check if this busy context is exclusive */
> if (tmp->exclusive_interface_modes &
> BIT(tmp->vif->type)) {
> @@ -1288,7 +1296,7 @@ static int iwlagn_mac_add_interface(struct ieee80211_hw *hw,
> ctx->vif = vif;
>
> err = iwl_setup_interface(priv, ctx);
> - if (!err)
> + if (!err || reset)
> goto out;
>
> ctx->vif = NULL;
next prev parent reply other threads:[~2012-03-13 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 15:10 [PATCH] iwlwifi: do not nulify ctx->vif on reset Stanislaw Gruszka
2012-03-13 15:15 ` Johannes Berg [this message]
2012-03-14 6:25 ` Stanislaw Gruszka
2012-03-14 6:58 ` Johannes Berg
2012-03-14 7:07 ` Stanislaw Gruszka
2012-03-14 8:14 ` Stanislaw Gruszka
2012-03-16 14:37 ` Stanislaw Gruszka
2012-03-16 15:16 ` Johannes Berg
2012-03-26 9:08 ` Johannes Berg
2012-03-26 14:30 ` Guy, Wey-Yi
2012-03-26 18:42 ` John W. Linville
2012-03-26 18:51 ` Guy, Wey-Yi
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=1331651730.3329.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ilw@linux.intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=sgruszka@redhat.com \
--cc=wey-yi.w.guy@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;
as well as URLs for NNTP newsgroup(s).