From: Kalle Valo <kvalo@codeaurora.org>
To: Krishna Chaitanya <chaitanya.mgit@gmail.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
ath10k <ath10k@lists.infradead.org>,
Wen Gong <wgong@codeaurora.org>
Subject: Re: [PATCH v3] ath10k: add flag to protect napi operation to avoid dead loop hang
Date: Wed, 09 Dec 2020 11:11:01 +0200 [thread overview]
Message-ID: <87wnxrbaze.fsf@codeaurora.org> (raw)
In-Reply-To: <CABPxzYKOCtA0n=bTHXT5VdsTGHcVc5PEvS2-TnGD9XEKCWdrNQ@mail.gmail.com> (Krishna Chaitanya's message of "Fri, 28 Aug 2020 19:39:11 +0530")
Krishna Chaitanya <chaitanya.mgit@gmail.com> writes:
> On Fri, Aug 28, 2020 at 5:53 PM Wen Gong <wgong@codeaurora.org> wrote:
>>
>> It happened "Kernel panic - not syncing: hung_task: blocked tasks" when
>> test simulate crash and ifconfig down/rmmod meanwhile.
(editing out hundreds of lines of unnecessary text, please edit your quotes)
> LGTM, except maybe a shorted title "ath10k: Prevent deinitializing NAPI twice".
Thanks, I fixed the title in the pending branch.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2020-12-09 9:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 12:22 [PATCH v3] ath10k: add flag to protect napi operation to avoid dead loop hang Wen Gong
2020-08-28 14:09 ` Krishna Chaitanya
2020-12-09 9:11 ` Kalle Valo [this message]
2020-09-07 16:23 ` Kalle Valo
[not found] ` <87d02x1rqb.fsf@codeaurora.org>
2020-09-08 3:45 ` Wen Gong
2020-12-09 9:24 ` Kalle Valo
2020-12-09 15:00 ` Ben Greear
2020-12-10 2:29 ` Wen Gong
2020-12-15 8:05 ` Kalle Valo
2020-12-15 7:56 ` Kalle Valo
2020-12-10 2:27 ` Wen Gong
2020-12-17 6:52 ` 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=87wnxrbaze.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath10k@lists.infradead.org \
--cc=chaitanya.mgit@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=wgong@codeaurora.org \
/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