From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933544AbXCONWb (ORCPT ); Thu, 15 Mar 2007 09:22:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933549AbXCONWb (ORCPT ); Thu, 15 Mar 2007 09:22:31 -0400 Received: from an-out-0708.google.com ([209.85.132.246]:13042 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933544AbXCONWa convert rfc822-to-8bit (ORCPT ); Thu, 15 Mar 2007 09:22:30 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=s/AkgvHcJlGeZGAiJKOC8A9oD8EzX4+MqAI7P2wdUiGxQRvIjkCj2/5NOknVnzSdLlVIYLZCDYun0gVZXxNXpM/Vg99G5L5isJnj2Qr5hyLFma+/2rlDxdqQ2yzCYfWgbw3jcvzlufn3osGNaxDRUuCyUY6/aJnAz7ZipMoqWGU= Message-ID: Date: Thu, 15 Mar 2007 09:22:25 -0400 From: "Dmitry Torokhov" To: "Oliver Neukum" Subject: Re: 2.6.21-rc suspend regression: sysfs deadlock Cc: "Hugh Dickins" , "Cornelia Huck" , "Alan Stern" , "Linus Torvalds" , "Maneesh Soni" , gregkh@suse.de, "Richard Purdie" , "James Bottomley" , "Kernel development list" In-Reply-To: <200703151402.08097.oneukum@suse.de> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8BIT Content-Disposition: inline References: <20070314194337.5d439dab@gondolin.boeblingen.de.ibm.com> <20070315112725.7eadb7b7@gondolin.boeblingen.de.ibm.com> <200703151402.08097.oneukum@suse.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On 3/15/07, Oliver Neukum wrote: > Am Donnerstag, 15. März 2007 13:31 schrieb Hugh Dickins: > > Quite apart from this mysterious "other task", I don't understand > > "access" either. > > > > Perhaps "defer" would best capture the idea of another-task and > > maybe-delay? sysfs_defer_work(), struct sysfs_deferred_work? > > But we do not wish to defer or delay anything. > How about: sysfs_action_from_neutral_context > How about sysfs_schedule_work? That is what it does - schedules a work on a sysfs object and everyone here knows what schedule_work() does. -- Dmitry