From: "Linus Lüssing" <linus.luessing@c0d3.blue>
To: linux-bluetooth@vger.kernel.org, linux-wireless@vger.kernel.org,
Intel Linux Wireless <linuxwifi@intel.com>
Cc: Emmanuel Grumbach <emmanuel.grumbach@intel.com>,
Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
Marcel Holtmann <marcel@holtmann.org>
Subject: Re: Crash / Null pointer dereference in l2cap_chan_send()
Date: Tue, 10 Nov 2020 21:59:50 +0100 [thread overview]
Message-ID: <20201110205950.GF2423@otheros> (raw)
In-Reply-To: <20201110062039.GC2423@otheros>
On Tue, Nov 10, 2020 at 07:20:39AM +0100, Linus Lüssing wrote:
> [...]
>
> The issue was introduced with the following commit:
>
> f4bfdc5e571e ("iwlwifi: mvm: stop supporting swcrypto and bt_coex_active module parameters")
> * first affected tag: v5.8-rc1
>
PS: As this commit mentioned bt_coex_active, I retried with a
vanilla 5.9.6 kernel while leaving bt_coex_active at its
default value. That is leaving it enabled while all previous tests
I did had it disabled.
However I still get the Bluetooth A2DP freeze and subsequent
kernel panics.
Only the warnings in dmesg with
"iwlmvm doesn't allow to disable BT Coex, check bt_coex_active module parameter"
seem to have vanished.
Also, swcrypto is disabled, as it is by default. So the majority
of the lines changed shouldn't affect me.
The only thing that should affect and trigger the crashes for me
seems to be that BT_COEX_NW is now always enabled and that the code
now ignores what I set for the iwlwifi bt_coex_active module parameter.
While before I had it always disabled via the iwlwifi module parameter.
next prev parent reply other threads:[~2020-11-10 21:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 6:20 Crash / Null pointer dereference in l2cap_chan_send() Linus Lüssing
2020-11-10 20:59 ` Linus Lüssing [this message]
2022-05-02 9:05 ` Linus Lüssing
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=20201110205950.GF2423@otheros \
--to=linus.luessing@c0d3.blue \
--cc=emmanuel.grumbach@intel.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linuxwifi@intel.com \
--cc=luiz.von.dentz@intel.com \
--cc=marcel@holtmann.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).