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
| ||
|
Date: Wed, 24 Aug 2022 15:40:38 +0200 From: Benjamin Tissoires <benjamin.tissoires@...hat.com> To: Greg KH <gregkh@...uxfoundation.org>, Jiri Kosina <jikos@...nel.org>, Alexei Starovoitov <ast@...nel.org>, Daniel Borkmann <daniel@...earbox.net>, Andrii Nakryiko <andrii@...nel.org>, Martin KaFai Lau <kafai@...com>, Song Liu <songliubraving@...com>, Yonghong Song <yhs@...com>, Kumar Kartikeya Dwivedi <memxor@...il.com>, John Fastabend <john.fastabend@...il.com>, KP Singh <kpsingh@...nel.org>, Shuah Khan <shuah@...nel.org>, Dave Marchevsky <davemarchevsky@...com>, Joe Stringer <joe@...ium.io>, Jonathan Corbet <corbet@....net> Cc: Tero Kristo <tero.kristo@...ux.intel.com>, linux-kernel@...r.kernel.org, linux-input@...r.kernel.org, netdev@...r.kernel.org, bpf@...r.kernel.org, linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org, Benjamin Tissoires <benjamin.tissoires@...hat.com> Subject: [PATCH bpf-next v9 08/23] HID: core: store the unique system identifier in hid_device This unique identifier is currently used only for ensuring uniqueness in sysfs. However, this could be handful for userspace to refer to a specific hid_device by this id. 2 use cases are in my mind: LEDs (and their naming convention), and HID-BPF. Reviewed-by: Greg Kroah-Hartman <gregkh@...uxfoundation.org> Signed-off-by: Benjamin Tissoires <benjamin.tissoires@...hat.com> --- no changes in v9 no changes in v8 no changes in v7 no changes in v6 new in v5 --- drivers/hid/hid-core.c | 4 +++- include/linux/hid.h | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c index b7f5566e338d..a00dd43db8bf 100644 --- a/drivers/hid/hid-core.c +++ b/drivers/hid/hid-core.c @@ -2739,10 +2739,12 @@ int hid_add_device(struct hid_device *hdev) hid_warn(hdev, "bad device descriptor (%d)\n", ret); } + hdev->id = atomic_inc_return(&id); + /* XXX hack, any other cleaner solution after the driver core * is converted to allow more than 20 bytes as the device name? */ dev_set_name(&hdev->dev, "%04X:%04X:%04X.%04X", hdev->bus, - hdev->vendor, hdev->product, atomic_inc_return(&id)); + hdev->vendor, hdev->product, hdev->id); hid_debug_register(hdev, dev_name(&hdev->dev)); ret = device_add(&hdev->dev); diff --git a/include/linux/hid.h b/include/linux/hid.h index 4363a63b9775..a43dd17bc78f 100644 --- a/include/linux/hid.h +++ b/include/linux/hid.h @@ -658,6 +658,8 @@ struct hid_device { /* device report descriptor */ struct list_head debug_list; spinlock_t debug_list_lock; wait_queue_head_t debug_wait; + + unsigned int id; /* system unique id */ }; #define to_hid_device(pdev) \ -- 2.36.1
Powered by blists - more mailing lists