From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Date: Thu, 08 Apr 2004 22:47:13 +0000 Subject: Re: [PATCH] call_usermodehelper hang Message-Id: <20040408224713.GD15125@kroah.com> List-Id: References: <4072F2B7.2070605@us.ibm.com> <20040406172903.186dd5f1.akpm@osdl.org> <20040407061146.GA10413@kroah.com> <407487A6.8020904@us.ibm.com> In-Reply-To: <407487A6.8020904@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Brian King Cc: Andrew Morton , linux-kernel@vger.kernel.org, linux-hotplug-devel@lists.sourceforge.net On Wed, Apr 07, 2004 at 05:58:46PM -0500, Brian King wrote: > The following patch fixes a deadlock experienced when devices are > being added to a bus both from a user process and eventd process. > The eventd process was hung waiting on dev->bus->subsys.rwsem which > was held by another process, which was hung since it was calling > call_usermodehelper directly which was hung waiting for work scheduled > on the eventd workqueue to complete. The patch fixes this by delaying > the kobject_hotplug work, running it from eventd if possible. But why? Will this not still cause the same deadlock eventually? The call_usermodehelper function uses keventd, so what about users who call that function directly? Also, you gratitously changed some of the whitespace in the file you were modifying, which isn't a nice thing to do :) thanks, greg k-h ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel