Received-SPF: pass (google.com: domain of linux-kernel+bounces-170209-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.80.249 as permitted sender) client-ip=147.75.80.249;
Content-Type: text/plain; charset="utf-8"
Precedence: bulk
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH v4] Bluetooth: L2CAP: Fix div-by-zero in
 l2cap_le_flowctl_init()
From: patchwork-bot+bluetooth@kernel.org
Message-Id: 
 <171501482813.13196.146367594390490315.git-patchwork-notify@kernel.org>
Date: Mon, 06 May 2024 17:00:28 +0000
References: <20240504192329.351126-1-iam@sung-woo.kim>
In-Reply-To: <20240504192329.351126-1-iam@sung-woo.kim>
To: Sungwoo Kim <iam@sung-woo.kim>
Cc: luiz.dentz@gmail.com, daveti@purdue.edu, benquike@gmail.com,
 marcel@holtmann.org, johan.hedberg@gmail.com, davem@davemloft.net,
 edumazet@google.com, kuba@kernel.org, pabeni@redhat.com,
 linux-bluetooth@vger.kernel.org, netdev@vger.kernel.org,
 linux-kernel@vger.kernel.org

Hello:

This patch was applied to bluetooth/bluetooth-next.git (master)
by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>:

On Sat,  4 May 2024 15:23:29 -0400 you wrote:
> l2cap_le_flowctl_init() can cause both div-by-zero and an integer
> overflow since hdev->le_mtu may not fall in the valid range.
> 
> Move MTU from hci_dev to hci_conn to validate MTU and stop the connection
> process earlier if MTU is invalid.
> Also, add a missing validation in read_buffer_size() and make it return
> an error value if the validation fails.
> Now hci_conn_add() returns ERR_PTR() as it can fail due to the both a
> kzalloc failure and invalid MTU value.
> 
> [...]

Here is the summary with links:
  - [v4] Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()
    https://git.kernel.org/bluetooth/bluetooth-next/c/93e31170f4d0

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html