linux-kernel - [git pull] Input updates for 2.6.37-rc1

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>] [day] [month] [year] [list]

Date:	Fri, 19 Nov 2010 09:18:43 -0800
From:	Dmitry Torokhov <dmitry.torokhov@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, linux-input@...r.kernel.org
Subject: [git pull] Input updates for 2.6.37-rc1

Hi Linus,

Please pull from:

	git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git for-linus
or
	master.kernel.org:/pub/scm/linux/kernel/git/dtor/input.git for-linus

to receive updates for the input subsystem.

There is a fix for keycode mapping regression affecting mostly
sony-laptop users; fix for regression in SysRq handling code causing it
to swallow lone Alt+SysRq (without any follow up action) so that print
screen shortcuts stopped working, and a patch that tightens security on
Aiptek sysfs attributes.

Changelog:
---------

Dmitry Torokhov (2):
      Input: sysrq - pass along lone Alt + SysRq
      Input: aiptek - tighten up permissions on sysfs attributes

Mattia Dongili (1):
      Input: fix typo in keycode validation supporting large scancodes


Diffstat:
--------

 drivers/input/input.c         |    2 +-
 drivers/input/tablet/aiptek.c |   28 ++++----
 drivers/tty/sysrq.c           |  169 ++++++++++++++++++++++++++++++-----------
 3 files changed, 139 insertions(+), 60 deletions(-)

-- 
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/