From: Duncan Laurie <dlaurie@chromium.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Duncan Laurie <dlaurie@chromium.org>
Subject: [PATCH] Input: serio - clear serio event queue after sysfs driver rebind
Date: Mon, 22 Nov 2010 15:09:50 -0800 [thread overview]
Message-ID: <1290467390-25302-1-git-send-email-dlaurie@chromium.org> (raw)
When rebinding a serio driver via sysfs drvctl interface it is possible for
an interrupt to trigger after the disconnect of the existing driver and
before the binding of the new driver. This will cause the serio interrupt
handler to queue a rescan event which will disconnect the new driver
immediately after it is attached.
This change clears the serio event queue after processing the drvctl
request but before releasing the serio mutex, which will clear any queued
rescans before they can get processed.
Reproduction involves issuing a rebind of device port from psmouse driver
to serio_raw driver while generating input to trigger interrupts. Then
checking to see if the corresponding i8042/serio4/driver is correctly
attached to the serio_raw driver instead of psmouse.
Signed-off-by: Duncan Laurie <dlaurie@chromium.org>
---
drivers/input/serio/serio.c | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/input/serio/serio.c b/drivers/input/serio/serio.c
index 405bf21..a66307e 100644
--- a/drivers/input/serio/serio.c
+++ b/drivers/input/serio/serio.c
@@ -454,6 +454,7 @@ static ssize_t serio_rebind_driver(struct device *dev, struct device_attribute *
serio_disconnect_port(serio);
error = serio_bind_driver(serio, to_serio_driver(drv));
put_driver(drv);
+ serio_remove_pending_events(serio);
} else {
error = -EINVAL;
}
--
1.7.3.1
next reply other threads:[~2010-11-22 23:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-22 23:09 Duncan Laurie [this message]
2010-11-27 8:41 ` [PATCH] Input: serio - clear serio event queue after sysfs driver rebind Dmitry Torokhov
2010-11-29 21:37 ` Duncan Laurie
2010-12-08 5:12 ` Dmitry Torokhov
2011-02-01 9:21 ` Dmitry Torokhov
2011-02-02 22:41 ` Duncan Laurie
2011-02-02 22:58 ` Dmitry Torokhov
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=1290467390-25302-1-git-send-email-dlaurie@chromium.org \
--to=dlaurie@chromium.org \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).