linux-kernel - Re: [PATCH] HID: use generic driver for ThingM blink(1) if !CONFIG_HID

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]

Date:	Mon, 3 Aug 2015 09:52:46 -0700
From:	Reilly Grant <reillyg@...omium.org>
To:	Jiri Kosina <jkosina@...e.com>
Cc:	Pavel Machek <pavel@....cz>, linux-input@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] HID: use generic driver for ThingM blink(1) if !CONFIG_HID_THINGM

If the software is using usbdevice_fs, no, it can simply detach the
kernel driver. If the software is using hidraw then this blacklist
becomes the issue because even if you unload the special driver the
generic HID driver won't load. Is there a mechanism in the HID
subsystem for drivers to build on top of the generic one instead of
replacing it?


On Mon, Aug 3, 2015, 2:25 AM Jiri Kosina <jkosina@...e.com> wrote:
>
> On Sun, 2 Aug 2015, Reilly Grant wrote:
>
> > There is existing user space software (not just mine, also from the
> > manufacturer) that does not use the special driver and instead uses hidraw
> > or usbdevice_fs to control the device. LED class driver support for this
> > device is useful but should be optional.
>
> Is there any problem for the userspace software to unbind the kernel
> driver first?
>
> --
> Jiri Kosina
> SUSE Labs
--
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/