Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Tue, 10 Nov 2020 21:59:50 +0100
From:   Linus =?utf-8?Q?L=C3=BCssing?= <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()
Message-ID: <20201110205950.GF2423@otheros>
References: <20201110062039.GC2423@otheros>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20201110062039.GC2423@otheros>
Precedence: bulk

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.