| 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
| ||
|
Message-Id: <200610081009.23978.dtor@insightbb.com> Date: Sun, 8 Oct 2006 10:09:22 -0400 From: Dmitry Torokhov <dtor@...ightbb.com> To: "Zephaniah E. Hull" <warp@...allh.com> Cc: "raise.sail@...il.com" <raise.sail@...il.com>, greg <greg@...ah.com>, Randy Dunlap <rdunlap@...otime.net>, LKML <linux-kernel@...r.kernel.org>, linux-usb-devel <linux-usb-devel@...ts.sourceforge.net> Subject: Re: [linux-usb-devel] [PATCH] usb/hid: The HID Simple Driver Interface 0.3.2 (core) On Sunday 08 October 2006 08:41, Zephaniah E. Hull wrote: > 0: If you keep all the ID identical, userspace may have the capabilities > cached. This may also cause problems, but if Dmitry or Greg calls that > a userspace bug I'll believe them and find a workaround. Yes, I'd consider it a bug. Tearing down and re-creating input device generates proper hotplug notifications and userspace needs to respect them as capabilities may change even if ids stay the same. For example playing with atkbd's scroll attribute will regenerate an input device with[out] scroll capabilities but its input_id structure will stay the same. ... Or were you talking about ids as in inputX? These are ever increasing as new devices get created and will never be reused (as long as atomic_t doesn't wrap around ;) ) -- Dmitry - 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/
Powered by blists - more mailing lists