From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dmitry Torokhov Subject: Re: [PATCH 2/3] input: use input_mutex instead of BKL when opening input device Date: Tue, 9 Mar 2010 22:20:15 -0800 Message-ID: <20100310062015.GA2445@core.coreip.homeip.net> References: <1268162386-2745-1-git-send-email-cascardo@holoscopio.com> <1268162386-2745-2-git-send-email-cascardo@holoscopio.com> <201003092112.14071.arnd@arndb.de> <20100309205947.GB1498@holoscopio.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mail-gw0-f46.google.com ([74.125.83.46]:39026 "EHLO mail-gw0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752735Ab0CJGUV (ORCPT ); Wed, 10 Mar 2010 01:20:21 -0500 Content-Disposition: inline In-Reply-To: <20100309205947.GB1498@holoscopio.com> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Thadeu Lima de Souza Cascardo Cc: Arnd Bergmann , linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, John Kacur On Tue, Mar 09, 2010 at 05:59:48PM -0300, Thadeu Lima de Souza Cascardo wrote: > On Tue, Mar 09, 2010 at 09:12:13PM +0100, Arnd Bergmann wrote: > > On Tuesday 09 March 2010, Thadeu Lima de Souza Cascardo wrote: > > > MODULE_AUTHOR("Vojtech Pavlik "); > > > @@ -1881,7 +1880,7 @@ static int input_open_file(struct inode *inode, struct file *file) > > > const struct file_operations *old_fops, *new_fops = NULL; > > > int err; > > > > > > - lock_kernel(); > > > + mutex_lock(&input_mutex); > > > /* No load-on-demand here? */ > > > handler = input_table[iminor(inode) >> 5]; > > > if (!handler || !(new_fops = fops_get(handler->fops))) { > > > @@ -1909,7 +1908,7 @@ static int input_open_file(struct inode *inode, struct file *file) > > > } > > > fops_put(old_fops); > > > out: > > > - unlock_kernel(); > > > + mutex_unlock(&input_mutex); > > > return err; > > > } > > > > > > -- > > > > Well, actually please have a look at > > http://git.kernel.org/?p=linux/kernel/git/arnd/playground.git;a=commitdiff;h=c06fd0234357618a5741ce958d58901ae4cb7ac1 > > > > * use mutex_lock_interruptible() where possible > > * you probably don't want to hold input_mutex when calling into the lower > > device's open function > > > > Arnd > > Yeah. I was just looking at your appointed branch. And I've noticed your > change was better. > > I was willing to let the open call go unprotected. But ended up checking > that the three callees were fine (they do not call any of the other > functions that take the mutex). > > Since the fops_put/fops_get do protect that section from the handler > removal and I can't think of any other race right now, I think your > version is really better. > > Acked-by: Thadeu Lima de Souza Cascardo > OK, applied 2 Thadeu's patches and one Arnd's. Thanks. -- Dmitry