linux-kernel - Re: [PATCH v2] Bluetooth: rfcomm: fix modem control handling

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: 
 <176125561099.3260295.2414265996830531276.git-patchwork-notify@kernel.org>
Date: Thu, 23 Oct 2025 21:40:10 +0000
From: patchwork-bot+bluetooth@...nel.org
To: Johan Hovold <johan@...nel.org>
Cc: luiz.dentz@...il.com, marcel@...tmann.org, johan.hedberg@...il.com,
 linux-bluetooth@...r.kernel.org, linux-kernel@...r.kernel.org,
 stable@...r.kernel.org
Subject: Re: [PATCH v2] Bluetooth: rfcomm: fix modem control handling

Hello:

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

On Thu, 23 Oct 2025 14:05:30 +0200 you wrote:
> The RFCOMM driver confuses the local and remote modem control signals,
> which specifically means that the reported DTR and RTS state will
> instead reflect the remote end (i.e. DSR and CTS).
> 
> This issue dates back to the original driver (and a follow-on update)
> merged in 2002, which resulted in a non-standard implementation of
> TIOCMSET that allowed controlling also the TS07.10 IC and DV signals by
> mapping them to the RI and DCD input flags, while TIOCMGET failed to
> return the actual state of DTR and RTS.
> 
> [...]

Here is the summary with links:
  - [v2] Bluetooth: rfcomm: fix modem control handling
    https://git.kernel.org/bluetooth/bluetooth-next/c/8d2c47aeb078

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