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-next>] [day] [month] [year] [list]
Date:	Wed, 23 Jun 2010 13:14:41 +0200
From:	"Henrik Rydberg" <rydberg@...omail.se>
To:	Dmitry Torokhov <dmitry.torokhov@...il.com>
Cc:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
	Jiri Kosina <jkosina@...e.cz>, Ping Cheng <pingc@...om.com>,
	Benjamin Tissoires <tissoire@...a.fr>,
	Chase Douglas <chase.douglas@...onical.com>,
	Rafi Rubin <rafi@...s.upenn.edu>,
	Henrik Rydberg <rydberg@...omail.se>
Subject: [PATCH 0/4] input: evdev: Dynamic buffers (rev5)

Hi Dmitry,

Please find enclosed the fifth version of the evdev buffer patches.

In this version, the buffer scheme is left intact, leaving a single
patch to make the client buffers dynamic. Mostly harmless.

The rest of the patches are rebased versions of what has already been
sent, and summarizes what seems to be needed to fix the original
buffer problem. The last patch is a bonus which fixes an old bug.

Thanks,
Henrik

Henrik Rydberg (5):
  input: evdev: Convert to dynamic event buffer (rev5)
  input: Use driver hint to compute the evdev buffer size (rev3)
  input: bcm5974: Set the average number of events per MT event packet
  hid-input: Use a larger event buffer for MT devices
  input: evdev: Never leave the client buffer empty after write

 drivers/hid/hid-input.c       |    3 +++
 drivers/input/evdev.c         |   33 ++++++++++++++++++++++++++++-----
 drivers/input/mouse/bcm5974.c |    2 ++
 include/linux/input.h         |   17 +++++++++++++++++
 4 files changed, 50 insertions(+), 5 deletions(-)

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

Powered by Openwall GNU/*/Linux Powered by OpenVZ