From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id A68CC3D6CBC for ; Mon, 23 Mar 2026 19:40:17 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774294817; cv=none; b=Pd8mWjTAvHpA4Lk+elyzgS+ILqnzpPqwMq5hHOmtddyVwnAu/ISuoOn4Ez01mfosXSIq4BH/kkgtRJ/yk+bLDer2Qh1LgCGHyNNfR4U3gwQyRspnp1NOr8weoJigLknwKrptR+Ef3enYFhN5h871a4FMl13SHFvY/xljWS/8Cwo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774294817; c=relaxed/simple; bh=io4lsODDYNXNgXCTZ5ZaSSJUNlYefcfv5H3mfk0yvnM=; h=Content-Type:MIME-Version:Subject:From:Message-Id:Date:References: In-Reply-To:To:Cc; b=Mivueyd300S7V25Xn2lK8dSmSN4INaE76Zf10vgK8PRVLUfYdQt7YkSmAgDzCNFqeBoBDNOI17dJEoRmlw4HZlbOLMhMjCpJ3M4u7D8PLKpZPy17xd8rFXzSF8vQenCyXhEBoD62GjJuX00fl0iiVUPk+0GWmjxg7TFeim45KQI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=hMY+ToXb; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="hMY+ToXb" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 64CE5C2BC87; Mon, 23 Mar 2026 19:40:17 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1774294817; bh=io4lsODDYNXNgXCTZ5ZaSSJUNlYefcfv5H3mfk0yvnM=; h=Subject:From:Date:References:In-Reply-To:To:Cc:From; b=hMY+ToXb5UPaqQfeQuKZzXuEIn1U7xoT55r1nH7nl/EYm753eoAXtKnHP24EPzar1 lFiM2AdMRx9CEHd4dOY8obgkJVSXkxYbRkUCK5hgxS2hdawhnRL4u94m1R+tvmFdAj p1GPDx5C1XbH1BDpl2K7geFC6iltM2Okv9/noR0A7spNv9+xvKju2hrayu4Puq8ZDU /1NIwFDOoW8Q9DytT3/4gd25YmcqDzL6QJSg0kYSuMSyDYEzRNzdjIrH1NqNrDU9co e3fPrdgjucVHV6z5PmF6SL11voryWtX54YeisVeKe2fhjj8q3iVqaJeFtcOsPtjLeS MlrhBTHJwDxjQ== Received: from [10.30.226.235] (localhost [IPv6:::1]) by aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org (Postfix) with ESMTP id 02EB43808200; Mon, 23 Mar 2026 19:40:07 +0000 (UTC) Content-Type: text/plain; charset="utf-8" Precedence: bulk X-Mailing-List: linux-bluetooth@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Subject: Re: [PATCH v2] Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop From: patchwork-bot+bluetooth@kernel.org Message-Id: <177429480578.286640.8792762831934128933.git-patchwork-notify@kernel.org> Date: Mon, 23 Mar 2026 19:40:05 +0000 References: In-Reply-To: To: Hyunwoo Kim Cc: marcel@holtmann.org, johan.hedberg@gmail.com, luiz.dentz@gmail.com, linux-bluetooth@vger.kernel.org Hello: This patch was applied to bluetooth/bluetooth-next.git (master) by Luiz Augusto von Dentz : On Fri, 20 Mar 2026 20:23:10 +0900 you wrote: > l2cap_config_req() processes CONFIG_REQ for channels in BT_CONNECTED > state to support L2CAP reconfiguration (e.g. MTU changes). However, > since both CONF_INPUT_DONE and CONF_OUTPUT_DONE are already set from > the initial configuration, the reconfiguration path falls through to > l2cap_ertm_init(), which re-initializes tx_q, srej_q, srej_list, and > retrans_list without freeing the previous allocations and sets > chan->sdu to NULL without freeing the existing skb. This leaks all > previously allocated ERTM resources. > > [...] Here is the summary with links: - [v2] Bluetooth: L2CAP: Fix ERTM re-init and zero pdu_len infinite loop https://git.kernel.org/bluetooth/bluetooth-next/c/acf374fce194 You are awesome, thank you! -- Deet-doot-dot, I am a bot. https://korg.docs.kernel.org/patchwork/pwbot.html