Linux bluetooth development
 help / color / mirror / Atom feed
From: patchwork-bot+bluetooth@kernel.org
To: Kyle Pepper <cochcoder@proton.me>
Cc: linux-bluetooth@vger.kernel.org, luiz.dentz@gmail.com,
	marcel@holtmann.org
Subject: Re: [PATCH v2 1/1] Bluetooth: reject invalid LE supervision timeout relationships
Date: Fri, 06 Nov 2026 20:20:09 +0000	[thread overview]
Message-ID: <179399640976.849577.17436810105504463448.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261106172404.591900-1-cochcoder@proton.me>

Hello:

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

On Fri, 06 Nov 2026 17:24:57 +0000 you wrote:
> The LE parameter validator calculates an unsigned maximum latency by
> subtracting one from a truncated quotient. If the quotient is zero,
> this wraps and accepts invalid parameters. Exact quotient boundaries
> also accept equality where the supervision timeout must be greater.
> 
> Compare the products directly after checking the field bounds. The
> validated interval and latency limits keep the products within int.
> This enforces the strict timeout relationship without division or
> unsigned subtraction.
> 
> [...]

Here is the summary with links:
  - [v2,1/1] Bluetooth: reject invalid LE supervision timeout relationships
    https://git.kernel.org/bluetooth/bluetooth-next/c/c1d50a71cdee

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



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

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-13  3:31 [RFC PATCH] Bluetooth: l2cap: honor local LE connection interval range Kyle Pepper
2026-10-13  4:26 ` [RFC] " bluez.test.bot
2026-10-13 14:33 ` [RFC PATCH] " Luiz Augusto von Dentz
2026-10-15 18:12   ` cochcoder
2026-10-15  4:34 ` [RFC PATCH v2] Bluetooth: l2cap: prefer compatible local LE intervals Kyle Pepper
2026-10-15  7:12   ` [RFC,v2] " bluez.test.bot
2026-10-15 18:11   ` [RFC PATCH v3] " Kyle Pepper
2026-10-15 20:17     ` [RFC,v3] " bluez.test.bot
2026-10-31 18:09     ` [RFC PATCH v3] " cochcoder
2026-11-06  2:18     ` [PATCH 1/1] Bluetooth: reject invalid LE supervision timeout relationships Kyle Pepper
2026-11-06  3:26       ` [1/1] " bluez.test.bot
2026-11-06  4:28       ` [PATCH 1/1] " cochcoder
2026-11-06 16:28       ` Luiz Augusto von Dentz
2026-11-06 17:24       ` [PATCH v2 " Kyle Pepper
2026-11-06 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=179399640976.849577.17436810105504463448.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+bluetooth@kernel.org \
    --cc=cochcoder@proton.me \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    /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