From mboxrd@z Thu Jan 1 00:00:00 1970 From: "KOSAKI Motohiro" Subject: Re: [PATCH] [14/18] BKL-removal: Add unlocked_fasync Date: Sun, 27 Jan 2008 16:05:47 +0900 Message-ID: <2f11576a0801262305r461e0b16s572ba224bc4cde4@mail.gmail.com> References: <20080127317.043953000@suse.de> <20080127021721.08AEA14D2E@wotan.suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org, akpm@osdl.org, kosaki.motohiro@gmail.com To: "Andi Kleen" Return-path: Received: from py-out-1112.google.com ([64.233.166.176]:19740 "EHLO py-out-1112.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751143AbYA0HFs (ORCPT ); Sun, 27 Jan 2008 02:05:48 -0500 Received: by py-out-1112.google.com with SMTP id u52so1820383pyb.10 for ; Sat, 26 Jan 2008 23:05:47 -0800 (PST) In-Reply-To: <20080127021721.08AEA14D2E@wotan.suse.de> Content-Disposition: inline Sender: linux-fsdevel-owner@vger.kernel.org List-ID: > Add a new fops entry point to allow fasync without BKL. While it's arguably > unclear this entry point is called often enough for it really matters > it was still relatively easy to do. And there are far less async users > in the tree than ioctls so it's likely they can be all converted > eventually and then the non unlocked async entry point could be dropped. Excellent! I like this patch :)