| 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: <4D4076FD.6070207@teksavvy.com> Date: Wed, 26 Jan 2011 14:33:17 -0500 From: Mark Lord <kernel@...savvy.com> To: Mauro Carvalho Chehab <mchehab@...hat.com> CC: Dmitry Torokhov <dmitry.torokhov@...il.com>, Linus Torvalds <torvalds@...ux-foundation.org>, Linux Kernel <linux-kernel@...r.kernel.org>, linux-input@...r.kernel.org, linux-media@...r.kernel.org Subject: Re: 2.6.36/2.6.37: broken compatibility with userspace input-utils ? On 11-01-26 12:32 PM, Mauro Carvalho Chehab wrote: > Em 26-01-2011 13:05, Mark Lord escreveu: .. >> Nope. Does not work here: >> >> $ lsinput >> protocol version mismatch (expected 65536, got 65537) > > You need to relax the version test at the tree. As I said before, this is > a development tool from the early RC days, bound to work with one specific > version of the API, and programmed by purpose to fail if there would by any > updates at the Input layer. .. As I said before, I personally have done that on my copy here. But that's not what this thread is about. This thread is about broken userspace courtesy of these changes. So I am testing with the original userspace binary here, and it still fails. And will continue to fail until that regression is fixed. Cheers -- 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