linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Luca Coelho <luca@coelho.fi>
Cc: linux-wireless@vger.kernel.org,
	Sara Sharon <sara.sharon@intel.com>,
	Luca Coelho <luciano.coelho@intel.com>
Subject: Re: [PATCH 6/6] iwlwifi: fix access to prph when transport is stopped
Date: Wed, 29 Nov 2017 12:23:55 +0200	[thread overview]
Message-ID: <87mv351iys.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <20171125153510.25359-7-luca@coelho.fi> (Luca Coelho's message of "Sat, 25 Nov 2017 17:35:10 +0200")

Luca Coelho <luca@coelho.fi> writes:

> From: Sara Sharon <sara.sharon@intel.com>
>
> When getting HW rfkill we get stop_device being called from
> two paths.
> One path is the IRQ calling stop device, and updating op
> mode and stack.
> As a result, cfg80211 is running rfkill sync work that shuts
> down all devices (second path).
> In the second path, we eventually get to iwl_mvm_stop_device
> which calls iwl_fw_dump_conf_clear->iwl_fw_dbg_stop_recording,
> that access periphery registers.
> The device may be stopped at this point from the first path,
> which will result with a failure to access those registers.
> Simply checking for the trans status is insufficient, since
> the race will still exist, only minimized.
> Instead, move the stop from iwl_fw_dump_conf_clear (which is
> getting called only from stop path) to the transport stop
> device function, where the access is always safe.
> This has the added value, of actually stopping dbgc before
> stopping device even when the stop is initiated from the
> transport.
>
> Fixes: 1efc3843a4ee ("iwlwifi: stop dbgc recording before stopping DMA")
> Signed-off-by: Sara Sharon <sara.sharon@intel.com>
> Signed-off-by: Luca Coelho <luciano.coelho@intel.com>

But no wonder I called gnus-article-fill-cited-article, the commit log
is just weirdly wrapped. Are you using outlook or how do you get it so
ugly? :)

-- 
Kalle Valo

  parent reply	other threads:[~2017-11-29 10:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25 15:35 [PATCH 0/6] iwlwifi: fixes intended for 4.15 2017-11-25 Luca Coelho
2017-11-25 15:35 ` [PATCH 1/6] iwlwifi: mvm: set correct chains in Rx status Luca Coelho
2017-11-25 15:35 ` [PATCH 2/6] iwlwifi: mvm: don't use transmit queue hang detection when it is not possible Luca Coelho
2017-11-25 15:35 ` [PATCH 3/6] iwlwifi: mvm: fix the TX queue hang timeout for MONITOR vif type Luca Coelho
2017-11-25 15:35 ` [PATCH 4/6] iwlwifi: mvm: fix packet injection Luca Coelho
2017-11-25 15:35 ` [PATCH 5/6] iwlwifi: pcie: fix erroneous "Read failed message" Luca Coelho
2017-11-25 15:35 ` [PATCH 6/6] iwlwifi: fix access to prph when transport is stopped Luca Coelho
2017-11-29 10:19   ` Kalle Valo
2017-11-29 10:21     ` Kalle Valo
2017-11-29 10:23   ` Kalle Valo [this message]
2017-11-29 10:29     ` Luca Coelho
2017-12-08 12:22       ` Kalle Valo
2017-12-08 12:26         ` Kalle Valo
2017-12-08 12:35           ` Luca Coelho
2017-12-08 12:56             ` Kalle Valo
2017-12-08 12:28         ` Luca Coelho

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=87mv351iys.fsf@kamboji.qca.qualcomm.com \
    --to=kvalo@codeaurora.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=luca@coelho.fi \
    --cc=luciano.coelho@intel.com \
    --cc=sara.sharon@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).