Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758325AbZLNVl6 (ORCPT ); Mon, 14 Dec 2009 16:41:58 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1757361AbZLNVlz (ORCPT ); Mon, 14 Dec 2009 16:41:55 -0500 Received: from smtp-out003.kontent.com ([81.88.40.217]:36203 "EHLO smtp-out003.kontent.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757273AbZLNVlx (ORCPT ); Mon, 14 Dec 2009 16:41:53 -0500 From: Oliver Neukum To: Alan Stern Subject: Re: Warn people about flush_scheduled_work() Date: Mon, 14 Dec 2009 22:42:06 +0100 User-Agent: KMail/1.12.2 (Linux/2.6.32-rc6-0.1-default; KDE/4.3.1; x86_64; ; ) Cc: Tejun Heo , Kernel development list References: In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200912142242.06633.oliver@neukum.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 619 Lines: 16 Am Montag, 14. Dezember 2009 22:33:38 schrieb Alan Stern: > Consider using cancel_work_sync() or cancel_delayed_work_sync() > instead. In most situations they will accomplish what you > need. In which respect is cancel_work_sync() fundamentally safer? If the work is already running and takes a lock you are holding, then what? Regards Oliver -- 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/