All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Amir Abudubai <amirabudubai@gmail.com>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org, surban@surban.net,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: Fix size check for receive buffer space
Date: Thu, 12 Nov 2026 20:20:05 +0000	[thread overview]
Message-ID: <179451480503.628769.12990613488160990578.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261111214905.518429-1-amirabudubai@gmail.com>

Hello:

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

On Wed, 11 Nov 2026 15:49:05 -0600 you wrote:
> Check that available receive space covers a full MTU-sized SDU and its
> overhead, rather than just the overhead. Otherwise, credits can be
> exhausted before an SDU is completed. This could result in a deadlock under
> some configurations and SDU combinations.
> 
> This follows the SDU-sized credit policy from commit 96cd8eaa131f
> ("Bluetooth: L2CAP: Derive rx credits from MTU and MPS"). Clarify the
> comment by replacing "packet" with "SDU".
> 
> [...]

Here is the summary with links:
  - Bluetooth: L2CAP: Fix size check for receive buffer space
    https://git.kernel.org/bluetooth/bluetooth-next/c/3b069de8a5d6

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



      parent reply	other threads:[~2026-11-12 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 21:49 [PATCH] Bluetooth: L2CAP: Fix size check for receive buffer space Amir Abudubai
2026-11-12  0:28 ` bluez.test.bot
2026-11-12 20:20 ` 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=179451480503.628769.12990613488160990578.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=amirabudubai@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    --cc=surban@surban.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.