* [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP
@ 2026-04-21 20:22 Luiz Augusto von Dentz
2026-04-21 21:26 ` [BlueZ,v1] " bluez.test.bot
2026-04-22 8:01 ` [PATCH BlueZ v1] " Bastien Nocera
0 siblings, 2 replies; 5+ messages in thread
From: Luiz Augusto von Dentz @ 2026-04-21 20:22 UTC (permalink / raw)
To: linux-bluetooth
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
HIDP is classic only, LE uses HOG, so there is no point in checking the
bonding with the address type which in case the device supports
dual-mode will map to LE random/public address.
Fixes: https://github.com/bluez/bluez/issues/2034
---
profiles/input/device.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/profiles/input/device.c b/profiles/input/device.c
index 6bdc5ee3aaf3..0ee6988c4e90 100644
--- a/profiles/input/device.c
+++ b/profiles/input/device.c
@@ -127,8 +127,7 @@ static int connection_disconnect(struct input_device *idev, uint32_t flags);
static bool input_device_bonded(struct input_device *idev)
{
- return device_is_bonded(idev->device,
- btd_device_get_bdaddr_type(idev->device));
+ return device_is_bonded(idev->device, BDADDR_BREDR);
}
static void input_device_free(struct input_device *idev)
--
2.53.0
^ permalink raw reply related [flat|nested] 5+ messages in thread
* RE: [BlueZ,v1] input: Fix checking LE bonding on HIDP
2026-04-21 20:22 [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP Luiz Augusto von Dentz
@ 2026-04-21 21:26 ` bluez.test.bot
2026-04-22 8:01 ` [PATCH BlueZ v1] " Bastien Nocera
1 sibling, 0 replies; 5+ messages in thread
From: bluez.test.bot @ 2026-04-21 21:26 UTC (permalink / raw)
To: linux-bluetooth, luiz.dentz
[-- Attachment #1: Type: text/plain, Size: 988 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1084033
---Test result---
Test Summary:
CheckPatch PASS 0.48 seconds
GitLint PASS 0.35 seconds
BuildEll PASS 20.23 seconds
BluezMake PASS 591.70 seconds
MakeCheck PASS 1.01 seconds
MakeDistcheck PASS 235.32 seconds
CheckValgrind PASS 201.19 seconds
CheckSmatch PASS 321.82 seconds
bluezmakeextell PASS 165.86 seconds
IncrementalBuild PASS 590.54 seconds
ScanBuild PASS 913.84 seconds
https://github.com/bluez/bluez/pull/2061
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP
2026-04-21 20:22 [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP Luiz Augusto von Dentz
2026-04-21 21:26 ` [BlueZ,v1] " bluez.test.bot
@ 2026-04-22 8:01 ` Bastien Nocera
2026-04-22 14:58 ` Luiz Augusto von Dentz
1 sibling, 1 reply; 5+ messages in thread
From: Bastien Nocera @ 2026-04-22 8:01 UTC (permalink / raw)
To: Luiz Augusto von Dentz, linux-bluetooth
On Tue, 2026-04-21 at 16:22 -0400, Luiz Augusto von Dentz wrote:
> From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
>
> HIDP is classic only, LE uses HOG, so there is no point in checking
> the
> bonding with the address type which in case the device supports
> dual-mode will map to LE random/public address.
>
> Fixes: https://github.com/bluez/bluez/issues/2034
> ---
> profiles/input/device.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/profiles/input/device.c b/profiles/input/device.c
> index 6bdc5ee3aaf3..0ee6988c4e90 100644
> --- a/profiles/input/device.c
> +++ b/profiles/input/device.c
> @@ -127,8 +127,7 @@ static int connection_disconnect(struct
> input_device *idev, uint32_t flags);
>
> static bool input_device_bonded(struct input_device *idev)
> {
> - return device_is_bonded(idev->device,
> - btd_device_get_bdaddr_type(idev-
> >device));
> + return device_is_bonded(idev->device, BDADDR_BREDR);
Do we want to do the same in virtual_cable_unplug() in that same file?
Do we also want to apply this to hog_accept() with BDADDR_LE in
profiles/input/hog.c ?
> }
>
> static void input_device_free(struct input_device *idev)
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP
2026-04-22 8:01 ` [PATCH BlueZ v1] " Bastien Nocera
@ 2026-04-22 14:58 ` Luiz Augusto von Dentz
0 siblings, 0 replies; 5+ messages in thread
From: Luiz Augusto von Dentz @ 2026-04-22 14:58 UTC (permalink / raw)
To: Bastien Nocera; +Cc: linux-bluetooth
Hi Bastien,
On Wed, Apr 22, 2026 at 4:01 AM Bastien Nocera <hadess@hadess.net> wrote:
>
> On Tue, 2026-04-21 at 16:22 -0400, Luiz Augusto von Dentz wrote:
> > From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
> >
> > HIDP is classic only, LE uses HOG, so there is no point in checking
> > the
> > bonding with the address type which in case the device supports
> > dual-mode will map to LE random/public address.
> >
> > Fixes: https://github.com/bluez/bluez/issues/2034
> > ---
> > profiles/input/device.c | 3 +--
> > 1 file changed, 1 insertion(+), 2 deletions(-)
> >
> > diff --git a/profiles/input/device.c b/profiles/input/device.c
> > index 6bdc5ee3aaf3..0ee6988c4e90 100644
> > --- a/profiles/input/device.c
> > +++ b/profiles/input/device.c
> > @@ -127,8 +127,7 @@ static int connection_disconnect(struct
> > input_device *idev, uint32_t flags);
> >
> > static bool input_device_bonded(struct input_device *idev)
> > {
> > - return device_is_bonded(idev->device,
> > - btd_device_get_bdaddr_type(idev-
> > >device));
> > + return device_is_bonded(idev->device, BDADDR_BREDR);
>
> Do we want to do the same in virtual_cable_unplug() in that same file?
Yep.
> Do we also want to apply this to hog_accept() with BDADDR_LE in
> profiles/input/hog.c ?
Not really. In the case of LE you really need to specify the address
type since there are multiple options: random versus public.
> > }
> >
> > static void input_device_free(struct input_device *idev)
--
Luiz Augusto von Dentz
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: [BlueZ,v1] input: Fix checking LE bonding on HIDP
2026-04-22 15:03 Luiz Augusto von Dentz
@ 2026-04-22 16:40 ` bluez.test.bot
0 siblings, 0 replies; 5+ messages in thread
From: bluez.test.bot @ 2026-04-22 16:40 UTC (permalink / raw)
To: linux-bluetooth, luiz.dentz
[-- Attachment #1: Type: text/plain, Size: 989 bytes --]
This is automated email and please do not reply to this email!
Dear submitter,
Thank you for submitting the patches to the linux bluetooth mailing list.
This is a CI test results with your patch series:
PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=1084336
---Test result---
Test Summary:
CheckPatch PASS 0.34 seconds
GitLint PASS 0.24 seconds
BuildEll PASS 20.31 seconds
BluezMake PASS 644.74 seconds
MakeCheck PASS 0.92 seconds
MakeDistcheck PASS 246.53 seconds
CheckValgrind PASS 221.43 seconds
CheckSmatch PASS 350.33 seconds
bluezmakeextell PASS 181.69 seconds
IncrementalBuild PASS 646.76 seconds
ScanBuild PASS 1025.97 seconds
https://github.com/bluez/bluez/pull/2062
---
Regards,
Linux Bluetooth
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2026-04-22 16:40 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-04-21 20:22 [PATCH BlueZ v1] input: Fix checking LE bonding on HIDP Luiz Augusto von Dentz
2026-04-21 21:26 ` [BlueZ,v1] " bluez.test.bot
2026-04-22 8:01 ` [PATCH BlueZ v1] " Bastien Nocera
2026-04-22 14:58 ` Luiz Augusto von Dentz
-- strict thread matches above, loose matches on Subject: below --
2026-04-22 15:03 Luiz Augusto von Dentz
2026-04-22 16:40 ` [BlueZ,v1] " bluez.test.bot
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.