linux-kernel - Re: [PATCH] Bluetooth: Keep a copy of each HID device's report descriptor.

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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 05 Feb 2010 09:51:43 -0800
From:	Marcel Holtmann <marcel@...tmann.org>
To:	Michael Poole <mdpoole@...ilus.org>
Cc:	Bastien Nocera <hadess@...ess.net>, Jiri Kosina <jkosina@...e.cz>,
	"Gunn, Brian" <bgunn@...ekai.com>, Ping <pinglinux@...il.com>,
	linux-kernel@...r.kernel.org,
	BlueZ development <linux-bluetooth@...r.kernel.org>
Subject: Re: [PATCH] Bluetooth: Keep a copy of each HID device's report
 descriptor.

Hi Michael,

> > looks good to me. I just prefer that you do the allocation of the report
> > descriptor before the HID object:
> 
> An updated patch is below.  Sorry for the delay -- inclement weather
> here got in the way of testing this as quickly as I would have liked.
> 
> From e245ef87247f5e257db40c412af7991c9af375ab Mon Sep 17 00:00:00 2001
> From: Michael Poole <mdpoole@...ilus.org>
> Date: Fri, 5 Feb 2010 12:21:38 -0500
> Subject: [PATCH] Bluetooth: Keep a copy of each HID device's report descriptor.
> 
> The report descriptor is read by user space (via the Service
> Discovery Protocol), so it is only available during the ioctl
> to connect.  However, the probe function that needs the
> descriptor might not be called until a specific module is
> loaded.  Keep a copy of the descriptor so it is available for
> later use.

patch has been applied. Thanks.

Regards

Marcel


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/