From: Pavel Machek <pavel@suse.cz>
To: Rusty trivial patch monkey Russell <trivial@rustcorp.com.au>,
vojtech@suse.cz, kernel list <linux-kernel@vger.kernel.org>
Subject: Fix locking in input
Date: Sat, 22 Nov 2003 16:52:24 +0100 [thread overview]
Message-ID: <20031122155224.GA249@elf.ucw.cz> (raw)
Hi!
input uses "volatile signed char" as a shared variable between normal
and interrupt threads (look at _sendbyte()). Thats bad idea, this
switches it to atomic_t.
I did not dare to store -1 o atomic ariable, that's why I switched -1
to +2.
I hope I do not break compilation somewhere, otherwise its trivial...
Pavel
--- tmp/linux/drivers/input/keyboard/98kbd.c 2003-04-21 22:31:32.000000000 +0200
+++ linux/drivers/input/keyboard/98kbd.c 2003-11-22 16:36:39.000000000 +0100
@@ -100,7 +100,7 @@
char phys[32];
unsigned char cmdbuf[4];
unsigned char cmdcnt;
- signed char ack;
+ atomic_t ack;
unsigned char shift;
struct {
unsigned char scancode;
@@ -118,10 +118,10 @@
switch (data) {
case KBD98_RET_ACK:
- kbd98->ack = 1;
+ atomic_set(&kbd98->ack, 1);
return;
case KBD98_RET_NAK:
- kbd98->ack = -1;
+ atomic_set(&kbd98->ack, 2);
return;
}
@@ -220,14 +220,14 @@
static int kbd98_sendbyte(struct kbd98 *kbd98, unsigned char byte)
{
int timeout = 10000; /* 100 msec */
- kbd98->ack = 0;
+ atomic_set(&kbd98->ack, 0);
if (serio_write(kbd98->serio, byte))
return -1;
- while (!kbd98->ack && timeout--) udelay(10);
+ while (!atomic_read(&kbd98->ack) && timeout--) udelay(10);
- return -(kbd98->ack <= 0);
+ return -(atomic_read(&kbd98->ack) == 2);
}
/*
--- tmp/linux/drivers/input/keyboard/atkbd.c 2003-10-26 13:08:37.000000000 +0100
+++ linux/drivers/input/keyboard/atkbd.c 2003-11-22 16:36:30.000000000 +0100
@@ -145,7 +145,7 @@
unsigned char set;
unsigned char release;
int lastkey;
- volatile signed char ack;
+ atomic_t ack;
unsigned char emul;
unsigned short id;
unsigned char write;
@@ -214,10 +214,10 @@
switch (code) {
case ATKBD_RET_ACK:
- atkbd->ack = 1;
+ atomic_set(&atkbd->ack, 1);
goto out;
case ATKBD_RET_NAK:
- atkbd->ack = -1;
+ atomic_set(&atkbd->ack, 2);
goto out;
}
@@ -294,7 +294,7 @@
static int atkbd_sendbyte(struct atkbd *atkbd, unsigned char byte)
{
int timeout = 20000; /* 200 msec */
- atkbd->ack = 0;
+ atomic_set(&atkbd->ack, 0);
#ifdef ATKBD_DEBUG
printk(KERN_DEBUG "atkbd.c: Sent: %02x\n", byte);
@@ -302,9 +302,9 @@
if (serio_write(atkbd->serio, byte))
return -1;
- while (!atkbd->ack && timeout--) udelay(10);
+ while (!atomic_read(&atkbd->ack) && timeout--) udelay(10);
- return -(atkbd->ack <= 0);
+ return -(atomic_read(&atkbd->ack) == 2);
}
/*
--- tmp/linux/drivers/input/mouse/psmouse-base.c 2003-09-28 22:05:48.000000000 +0200
+++ linux/drivers/input/mouse/psmouse-base.c 2003-11-22 16:15:12.000000000 +0100
@@ -121,13 +121,14 @@
if (psmouse->acking) {
switch (data) {
case PSMOUSE_RET_ACK:
- psmouse->ack = 1;
+ atomic_set(&psmouse->ack, 1);
break;
case PSMOUSE_RET_NAK:
- psmouse->ack = -1;
+ atomic_set(&psmouse->ack, 2);
break;
default:
- psmouse->ack = 1; /* Workaround for mice which don't ACK the Get ID command */
+ /* Workaround for mice which don't ACK the Get ID command */
+ atomic_set(&psmouse->ack, 1);
if (psmouse->cmdcnt)
psmouse->cmdbuf[--psmouse->cmdcnt] = data;
break;
@@ -197,7 +198,7 @@
static int psmouse_sendbyte(struct psmouse *psmouse, unsigned char byte)
{
int timeout = 10000; /* 100 msec */
- psmouse->ack = 0;
+ atomic_set(&psmouse->ack, 0);
psmouse->acking = 1;
if (serio_write(psmouse->serio, byte)) {
@@ -205,9 +206,9 @@
return -1;
}
- while (!psmouse->ack && timeout--) udelay(10);
+ while (!atomic_read(&psmouse->ack) && timeout--) udelay(10);
- return -(psmouse->ack <= 0);
+ return -(atomic_read(&psmouse->ack) == 2);
}
/*
--- tmp/linux/drivers/input/mouse/psmouse.h 2003-09-28 22:05:48.000000000 +0200
+++ linux/drivers/input/mouse/psmouse.h 2003-11-22 16:08:01.000000000 +0100
@@ -37,7 +37,7 @@
unsigned long last;
unsigned char state;
char acking;
- volatile char ack;
+ atomic_t ack; /* This is being accessed without locking, at least make sure we do not run into alignment problems */
char error;
char devname[64];
char phys[32];
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next reply other threads:[~2003-11-22 17:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-22 15:52 Pavel Machek [this message]
2003-11-23 21:51 ` Fix locking in input Paul Mackerras
[not found] ` <20031123134140.GE22591@vana.vc.cvut.cz>
2003-11-24 11:05 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2003-11-23 22:24 Manfred Spraul
2003-11-23 22:34 ` Russell King
2003-11-23 22:54 ` Manfred Spraul
2003-12-03 23:44 ` Timothy Miller
2003-12-04 1:29 ` Linus Torvalds
2003-11-24 9:34 ` Pavel Machek
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=20031122155224.GA249@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=trivial@rustcorp.com.au \
--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