From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757656AbZEVSaH (ORCPT ); Fri, 22 May 2009 14:30:07 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753488AbZEVS35 (ORCPT ); Fri, 22 May 2009 14:29:57 -0400 Received: from mail-fx0-f168.google.com ([209.85.220.168]:50264 "EHLO mail-fx0-f168.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753419AbZEVS35 convert rfc822-to-8bit (ORCPT ); Fri, 22 May 2009 14:29:57 -0400 X-Greylist: delayed 322 seconds by postgrey-1.27 at vger.kernel.org; Fri, 22 May 2009 14:29:56 EDT MIME-Version: 1.0 In-Reply-To: References: From: Kay Sievers Date: Fri, 22 May 2009 20:24:15 +0200 Message-ID: Subject: Re: How to tell whether a struct file is held by a process? To: Alan Stern Cc: Alan Cox , Kyle Moffett , Pantelis Koukousoulas , Al Viro , Kernel development list Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, May 22, 2009 at 17:54, Alan Stern wrote: >> Would releasing the "lock" trigger a kernel-driver-binding call? > > No.  If the lock owner wants to bind kernel drivers, it can use the > existing API in libusb after releasing the lock.  This might cause > problems if the owning process terminates abnormally, but I think we > can live with that. > >> The lock will always lock all devices of a specific hub? > > The idea is that there will be one lock file per port.  So for example, > a hub device with four ports might contain inside its sysfs device > directory: ports/1, ..., ports/4. Sounds both good to me. Kay