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]
Message-ID: <alpine.LNX.2.00.0905010103550.5012@wotan.suse.de>
Date:	Fri, 1 May 2009 01:09:12 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Oliver Neukum <oliver@...kum.org>
Cc:	Guillaume Chazarain <guichaz@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: What's in hid.git for 2.6.30

On Fri, 1 May 2009, Oliver Neukum wrote:

> > --- a/drivers/hid/hid-core.c
> > +++ b/drivers/hid/hid-core.c
> > @@ -1824,6 +1824,9 @@ int hid_check_keys_pressed(struct hid_device *hid)
> >         struct hid_input *hidinput;
> >         int i;
> >  
> > +       if (!(hid->claimed & HID_CLAIMED_INPUT))
> > +               return 0;
> > +
> is there a guarantee all keyboards will be claimed as input devices?

Hi Oliver,

do you see any way how hid->inputs could currently be initialized other 
than the device being claimed by hid-input?

-- 
Jiri Kosina
SUSE Labs

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ