mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
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
Subject: Re: [PATCH v4] Bluetooth: L2CAP: Fix div-by-zero in l2cap_le_flowctl_init()
Date: Mon, 06 May 2024 17:00:28 +0000	[thread overview]
Message-ID: <171501482813.13196.146367594390490315.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240504192329.351126-1-iam@sung-woo.kim>

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



      reply	other threads:[~2024-05-06 17:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-04 19:23 Sungwoo Kim
2024-05-06 17:00 ` patchwork-bot+bluetooth [this message]

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=171501482813.13196.146367594390490315.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=benquike@gmail.com \
    --cc=davem@davemloft.net \
    --cc=daveti@purdue.edu \
    --cc=edumazet@google.com \
    --cc=iam@sung-woo.kim \
    --cc=johan.hedberg@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    /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
all inboxes | Powered by JetHome®