public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: "Gunter Königsmann" <gunter.koenigsmann@gmx.de>,
	"Gunter Königsmann" <gunter@peterpall.de>
Cc: linux-kernel@vger.kernel.org, Vojtech Pavlik <vojtech@suse.cz>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 2/2] Psmouse log and discard timed out bytes
Date: Sat, 10 Jan 2004 03:46:03 -0500	[thread overview]
Message-ID: <200401100346.04660.dtor_core@ameritech.net> (raw)
In-Reply-To: <200401100345.17211.dtor_core@ameritech.net>

===================================================================


ChangeSet@1.1513, 2004-01-10 02:52:04-05:00, dtor_core@ameritech.net
  Input: psmouse - if keyboard controller reports a timeout or a parity error
         do not try to process the byte, log the problem and drop it early.


 psmouse-base.c |    7 +++++++
 1 files changed, 7 insertions(+)


===================================================================



diff -Nru a/drivers/input/mouse/psmouse-base.c b/drivers/input/mouse/psmouse-base.c
--- a/drivers/input/mouse/psmouse-base.c	Sat Jan 10 03:23:08 2004
+++ b/drivers/input/mouse/psmouse-base.c	Sat Jan 10 03:23:08 2004
@@ -121,6 +121,13 @@
 	if (psmouse->state == PSMOUSE_IGNORE)
 		goto out;
 
+	if (flags & (SERIO_PARITY|SERIO_TIMEOUT)) {
+		printk(KERN_WARNING "psmouse.c: bad data from KBC -%s%s\n",
+			flags & SERIO_TIMEOUT ? " timeout" : "",
+			flags & SERIO_PARITY ? " bad parity" : "");
+		goto out;
+	}
+
 	if (psmouse->acking) {
 		switch (data) {
 			case PSMOUSE_RET_ACK:

  reply	other threads:[~2004-01-10  8:48 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-09 10:17 Synaptics Touchpad workaround for strange behavior after Sync loss (With Patch) Gunter Königsmann
2004-01-09 10:58 ` Vojtech Pavlik
2004-01-10 22:50   ` Peter Berg Larsen
2004-01-11  2:39     ` Peter Berg Larsen
2004-01-11  3:33       ` Dmitry Torokhov
2004-01-11  8:37       ` Gunter Königsmann
2004-01-11 12:52         ` Peter Berg Larsen
2004-01-11 14:22           ` Vojtech Pavlik
2004-01-11 15:34             ` Dmitry Torokhov
2004-01-11 15:06           ` Gunter Königsmann
2004-01-11  8:10     ` Vojtech Pavlik
2004-01-11 12:46       ` Peter Berg Larsen
2004-01-11 14:21         ` Vojtech Pavlik
2004-01-19 22:25         ` Vojtech Pavlik
2004-01-10  8:44 ` Dmitry Torokhov
2004-01-10  8:45   ` [PATCH 1/2] Synaptics rate switching Dmitry Torokhov
2004-01-10  8:46     ` Dmitry Torokhov [this message]
2004-01-10 13:05       ` [PATCH 2/2] Psmouse log and discard timed out bytes Gunter Königsmann
2004-01-10 13:23       ` Gunter Königsmann
2004-01-11  4:57       ` [PATCH 3/2] Psmouse log and discard timed out bytes - addition Dmitry Torokhov
2004-01-11  8:11         ` Gunter Königsmann
2004-01-10  9:56     ` [PATCH 1/2] Synaptics rate switching Vojtech Pavlik
2004-01-10 22:05     ` Gunter Königsmann
2004-01-10 23:37       ` Vojtech Pavlik
2004-01-11  2:20       ` Dmitry Torokhov
2004-01-11  8:00         ` Gunter Königsmann

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200401100346.04660.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=gunter.koenigsmann@gmx.de \
    --cc=gunter@peterpall.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vojtech@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox