From: Dmitry Torokhov <dtor_core@ameritech.net>
To: Al Viro <viro@parcelfarce.linux.theplanet.co.uk>
Cc: Vojtech Pavlik <vojtech@suse.cz>,
Roman Zippel <zippel@linux-m68k.org>,
Andries Brouwer <aebr@win.tue.nl>,
linux-kernel@vger.kernel.org
Subject: Re: Possible bug in keyboard.c (2.6.10)
Date: Sun, 30 Jan 2005 18:21:53 -0500 [thread overview]
Message-ID: <200501301821.53924.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050130084154.GU8859@parcelfarce.linux.theplanet.co.uk>
On Sunday 30 January 2005 03:41, Al Viro wrote:
> On Sat, Jan 29, 2005 at 12:25:10PM +0100, Vojtech Pavlik wrote:
> > I know. As I said, this is a problem I know about, and will be fixed. I
> > was mainly interested whether anyone sees further problems in scenarios
> > which don't include device addition/removal.
> >
> > We already fixed this in serio, and input and gameport are next in the
> > list.
>
> OK, I'll bite. What's to guarantee that no events will happen in
> the middle of serio_unregister_port(), right after we'd done
> serio_remove_pending_events()?
At this point serio is disconnected from driver and serio_interrupt
will only queue rescans only if serio->registered. I guess I will need
to protect change to serio->registered and take serio->lock to be
completely in clear.
Thanks for pointing this out.
--
Dmitry
next prev parent reply other threads:[~2005-01-30 23:22 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-27 3:16 Possible bug in keyboard.c (2.6.10) Sasa Stevanovic
2005-01-27 4:50 ` Dmitry Torokhov
2005-01-27 10:16 ` Sasa Stevanovic
2005-01-27 12:56 ` Andries Brouwer
2005-01-28 0:39 ` Roman Zippel
2005-01-28 10:59 ` Vojtech Pavlik
2005-01-29 4:50 ` Al Viro
2005-01-29 11:25 ` Vojtech Pavlik
2005-01-29 23:35 ` Dmitry Torokhov
2005-01-31 9:01 ` Vojtech Pavlik
2005-01-30 8:41 ` Al Viro
2005-01-30 23:21 ` Dmitry Torokhov [this message]
2005-01-30 23:29 ` Dmitry Torokhov
2005-02-03 6:54 ` Dmitry Torokhov
2005-01-29 12:11 ` Roman Zippel
2005-01-29 14:04 ` Vojtech Pavlik
2005-01-30 20:13 ` Roman Zippel
2005-01-28 11:10 ` Vojtech Pavlik
2005-01-28 21:59 ` Andries Brouwer
2005-01-29 11:12 ` Vojtech Pavlik
2005-01-29 23:30 ` Dmitry Torokhov
2005-01-30 23:16 ` 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=200501301821.53924.dtor_core@ameritech.net \
--to=dtor_core@ameritech.net \
--cc=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=vojtech@suse.cz \
--cc=zippel@linux-m68k.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