linux-kernel - Re: [PATCH] Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: 
 <173818203201.417583.10236619568637892434.git-patchwork-notify@kernel.org>
Date: Wed, 29 Jan 2025 20:20:32 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Fedor Pchelkin <pchelkin@...ras.ru>
Cc: luiz.dentz@...il.com, linux-bluetooth@...r.kernel.org,
 marcel@...tmann.org, johan.hedberg@...il.com, linux-kernel@...r.kernel.org,
 lvc-project@...uxtesting.org, stable@...r.kernel.org
Subject: Re: [PATCH] Bluetooth: L2CAP: accept zero as a special value for MTU
 auto-selection

Hello:

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

On Wed, 29 Jan 2025 00:08:14 +0300 you wrote:
> One of the possible ways to enable the input MTU auto-selection for L2CAP
> connections is supposed to be through passing a special "0" value for it
> as a socket option. Commit [1] added one of those into avdtp. However, it
> simply wouldn't work because the kernel still treats the specified value
> as invalid and denies the setting attempt. Recorded BlueZ logs include the
> following:
> 
> [...]

Here is the summary with links:
  - Bluetooth: L2CAP: accept zero as a special value for MTU auto-selection
    https://git.kernel.org/bluetooth/bluetooth-next/c/257a2b95631f

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