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 for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAKdAkRSyv_n3K2YmqT7HdbaW07NzZSSsw01E_xcuyLoUKF4r1g@mail.gmail.com>
Date:   Sun, 22 Oct 2017 09:37:34 -0700
From:   Dmitry Torokhov <dmitry.torokhov@...il.com>
To:     Damien Wyart <damien.wyart@...il.com>
Cc:     Roderick Colenbrander <roderick.colenbrander@...y.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: Current git has USB keyboard and mouse unusable

On Sun, Oct 22, 2017 at 8:46 AM, Damien Wyart <damien.wyart@...il.com> wrote:
> Hi,
>
> Having compiled a kernel today (bfc1168de949c in Linus' tree), I
> noticed keyboard and mouse were not working at all (stuck at X DM
> level).
>
> After digging a bit, I realized only one change in the recent input
> commits was quite general, and bingo, reverting "allow matching device
> IDs on property bits" (8724ecb072293f109) made input work again.
>
> I did not find anything special in the logs for the bad kernel...
>
> Should that commit be reverted for now? Maybe other people will be
> able to reproduce it?

Hm, that is not good. A few question before we decide to revert:

- do your devices work on text console?
- can you post /proc/bus/input/devices to see if event handlers bind
to the device?
- is evdev driver in your kernel compiled as a module?

Thanks.

-- 
Dmitry

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ