All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Xinming Hu <huxm@marvell.com>
Cc: Linux Wireless <linux-wireless@vger.kernel.org>,
	Brian Norris <briannorris@chromium.org>,
	Dmitry Torokhov <dtor@google.com>, <rajatja@google.com>,
	Zhiyuan Yang <yangzy@marvell.com>, Tim Song <songtao@marvell.com>,
	Cathy Luo <cluo@marvell.com>, James Cao <jcao@marvell.com>,
	Ganapathi Bhat <gbhat@marvell.com>,
	Ellie Reeves <ellierevves@gmail.com>,
	Xinming Hu <huxm@marvell.com>
Subject: Re: mwifiex: cancel pcie/sdio work in remove/shutdown handler
Date: Mon,  8 Jan 2018 17:38:33 +0000 (UTC)	[thread overview]
Message-ID: <20180108173833.5B3046077A@smtp.codeaurora.org> (raw)
In-Reply-To: <1513164473-13827-1-git-send-email-huxm@marvell.com>

Xinming Hu <huxm@marvell.com> wrote:

> The last command used to shutdown firmware might be timeout,
> and trigger firmware dump in asynchronous pcie/sdio work.
> 
> The remove/shutdown handler will continue free core data
> structure private/adapter, which might be dereferenced in
> pcie/sdio work, finally crash the kernel.
> 
> Sync and Cancel pcie/sdio work, could be a fix for above
> cornel case. In this way, the last command timeout could
> be handled properly.
> 
> Signed-off-by: Xinming Hu <huxm@marvell.com>

Patch applied to wireless-drivers-next.git, thanks.

b713bbf1471b mwifiex: cancel pcie/sdio work in remove/shutdown handler

-- 
https://patchwork.kernel.org/patch/10109773/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

  reply	other threads:[~2018-01-08 17:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-13 11:27 [PATCH] mwifiex: cancel pcie/sdio work in remove/shutdown handler Xinming Hu
2018-01-08 17:38 ` Kalle Valo [this message]
2018-01-08 18:11 ` Brian Norris
2018-01-09  7:39   ` Kalle Valo

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=20180108173833.5B3046077A@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=briannorris@chromium.org \
    --cc=cluo@marvell.com \
    --cc=dtor@google.com \
    --cc=ellierevves@gmail.com \
    --cc=gbhat@marvell.com \
    --cc=huxm@marvell.com \
    --cc=jcao@marvell.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rajatja@google.com \
    --cc=songtao@marvell.com \
    --cc=yangzy@marvell.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.