From: Alexander Aring <alex.aring@gmail.com>
To: linux-wpan@vger.kernel.org
Cc: kernel@pengutronix.de, Michael Hennerich <michael.hennerich@analog.com>
Subject: Re: [PATCH bluetooth] mac802154: tx: fix synced xmit deadlock
Date: Wed, 9 Dec 2015 23:18:08 +0100 [thread overview]
Message-ID: <20151209221807.GA16100@omega> (raw)
In-Reply-To: <1449699331-17563-1-git-send-email-alex.aring@gmail.com>
Hi Marcel,
On Wed, Dec 09, 2015 at 11:15:31PM +0100, Alexander Aring wrote:
> This patch reverts 6001d52 ("mac802154: tx: don't allow if down while
> sync tx"). This has side effects with stop callback which flush the
> transmit workqueue. The stop callback will wait until the workqueue is
> flushed and holding the rtnl lock. That means it can happen that the stop
> callback waits forever because it try to lock the rtnl mutex which is
> already hold by stop callback.
>
wrong patch here, I will send a v2 which also remove the ASSERT_RTNL
while synced xmit driver callback.
- Alex
prev parent reply other threads:[~2015-12-09 22:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-09 22:15 [PATCH bluetooth] mac802154: tx: fix synced xmit deadlock Alexander Aring
2015-12-09 22:18 ` Alexander Aring [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=20151209221807.GA16100@omega \
--to=alex.aring@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-wpan@vger.kernel.org \
--cc=michael.hennerich@analog.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