From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: <ath10k@lists.infradead.org>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH/RFT v2 0/4] ath10k: fixes
Date: Tue, 8 Oct 2013 22:17:30 +0300 [thread overview]
Message-ID: <87ob6zr2r9.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1380865425-3791-1-git-send-email-michal.kazior@tieto.com> (Michal Kazior's message of "Fri, 4 Oct 2013 07:43:41 +0200")
Michal Kazior <michal.kazior@tieto.com> writes:
> Hi,
>
> This patchset addresses recently spotted issue
> with (yet another) scheduling while atomic bug
> (the other being WEP key index setting). This one
> is related to hw_config() and powersave settings.
> This comes from recent changes I've done to
> HTC/WMI. WMI commands can block now so it's
> illegal to call them in an atomic context anymore.
>
> ath10k needs to setup some settings per-vdev (i.e.
> per-interface) such as powersave, rts, fragmentation.
> Until now mac80211 iteration functions were used.
> However using non-atomic iteration function variant
> doesn't solve the problem as it introduces an
> issue with iflist_mtx deadlock in some cases.
>
> I briefly tried to reproduce the issue Kalle
> reported but was unsuccessful thus the "/RFT".
>
> v2:
> * fix kbuild test robot warning
> (uninitialized `ret`)
> * add patch #4 that removes code that becomes
> unnecessary after patch #3
>
>
> Michal Kazior (4):
> ath10k: fix add_interface failure handling
> ath10k: track vif list internally
> ath10k: fix scheduling while atomic config bug
> ath10k: remove unnecessary checks
Due to problems with patch 1 I'm dropping this patchset for now.
--
Kalle Valo
prev parent reply other threads:[~2013-10-08 19:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 13:09 [PATCH/RFT 0/3] ath10k: fixes Michal Kazior
2013-10-03 13:09 ` [PATCH/RFT 1/3] ath10k: fix add_interface failure handling Michal Kazior
2013-10-03 13:09 ` [PATCH/RFT 2/3] ath10k: track vif list internally Michal Kazior
2013-10-03 13:09 ` [PATCH/RFT 3/3] ath10k: fix scheduling while atomic config bug Michal Kazior
2013-10-04 5:43 ` [PATCH/RFT v2 0/4] ath10k: fixes Michal Kazior
2013-10-04 5:43 ` [PATCH/RFT v2 1/4] ath10k: fix add_interface failure handling Michal Kazior
2013-10-08 12:54 ` Kalle Valo
2013-10-08 16:49 ` Michal Kazior
2013-10-08 19:16 ` Kalle Valo
2013-10-09 2:59 ` Michal Kazior
2013-10-04 5:43 ` [PATCH/RFT v2 2/4] ath10k: track vif list internally Michal Kazior
2013-10-04 5:43 ` [PATCH/RFT v2 3/4] ath10k: fix scheduling while atomic config bug Michal Kazior
2013-10-04 5:43 ` [PATCH/RFT v2 4/4] ath10k: remove unnecessary checks Michal Kazior
2013-10-08 19:17 ` Kalle Valo [this message]
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=87ob6zr2r9.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.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