Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262825AbVBCGzE (ORCPT ); Thu, 3 Feb 2005 01:55:04 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262473AbVBCGzE (ORCPT ); Thu, 3 Feb 2005 01:55:04 -0500 Received: from smtp814.mail.sc5.yahoo.com ([66.163.170.84]:4204 "HELO smtp814.mail.sc5.yahoo.com") by vger.kernel.org with SMTP id S262825AbVBCGy4 (ORCPT ); Thu, 3 Feb 2005 01:54:56 -0500 From: Dmitry Torokhov To: Al Viro Subject: Re: Possible bug in keyboard.c (2.6.10) Date: Thu, 3 Feb 2005 01:54:51 -0500 User-Agent: KMail/1.7.2 Cc: Vojtech Pavlik , Roman Zippel , Andries Brouwer , linux-kernel@vger.kernel.org References: <20050130084154.GU8859@parcelfarce.linux.theplanet.co.uk> <200501301821.53924.dtor_core@ameritech.net> In-Reply-To: <200501301821.53924.dtor_core@ameritech.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502030154.52660.dtor_core@ameritech.net> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1357 Lines: 31 On Sunday 30 January 2005 18:21, Dmitry Torokhov wrote: > 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. > Thinking about it some more - serio driver should take care of shutting off interrupt delivery either in ->close() or ->stop() methods so we don't really need to worry about having new events delivered here. -- Dmitry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/