From: "Peer, Ilan" <ilan.peer@intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
Johannes Berg <johannes@sipsolutions.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Coelho, Luciano" <luciano.coelho@intel.com>
Subject: RE: pull-request: mac80211 2021-01-18.2
Date: Sun, 24 Jan 2021 13:03:28 +0000 [thread overview]
Message-ID: <BYAPR11MB2613A16DAF4DAC8A21643E4DE9BE9@BYAPR11MB2613.namprd11.prod.outlook.com> (raw)
In-Reply-To: <348210d8-6940-ca8d-e3b1-f049330a2087@redhat.com>
Hi,
> Great, thank you for looking into this. Let me know if you have a patch which
> you want me to test on a RTL8723BS adapter.
>
> One thing which I forgot to mention earlier, it is not just lockdep complaining
> this appears to be a real deadlock, the wifi no longer functions, where as it
> does function with the patch drops.
>
Agree.
Johannes,
Based on the latest changes you introduced in mac80211-next, the RTNL lock is not really required and can be removed. Would this be sufficient, or would you prefer a fix regardless of these changes?
Thanks in advance,
Ilan.
next prev parent reply other threads:[~2021-01-24 13:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-18 20:47 pull-request: mac80211 2021-01-18.2 Johannes Berg
2021-01-18 22:50 ` patchwork-bot+netdevbpf
2021-01-20 17:59 ` Johannes Berg
2021-01-20 20:37 ` Jakub Kicinski
2021-01-20 20:39 ` Johannes Berg
2021-01-23 21:31 ` Hans de Goede
2021-01-23 22:15 ` Johannes Berg
2021-01-24 9:12 ` Peer, Ilan
2021-01-24 10:54 ` Hans de Goede
2021-01-24 13:03 ` Peer, Ilan [this message]
2021-01-25 9:47 ` Johannes Berg
2021-01-25 11:18 ` Hans de Goede
2021-01-25 12:40 ` Johannes Berg
2021-01-25 12:59 ` Hans de Goede
2021-01-25 13:03 ` Johannes Berg
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=BYAPR11MB2613A16DAF4DAC8A21643E4DE9BE9@BYAPR11MB2613.namprd11.prod.outlook.com \
--to=ilan.peer@intel.com \
--cc=hdegoede@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=luciano.coelho@intel.com \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).