From: Arnd Bergmann Subject: Re: [PATCH] Remove BKL from fs/locks.c Date: Tue, 14 Sep 2010 23:24:15 +0200 Message-ID: <201009142324.16074.arnd@arndb.de> References: <201009142206.54130.arnd@arndb.de> <201009142239.02904.arnd@arndb.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, Matthew Wilcox , Christoph Hellwig , Trond Myklebust , "J. Bruce Fields" , Miklos Szeredi , Frederic Weisbecker , Ingo Molnar , John Kacur , Stephen Rothwell , Andrew Morton , Thomas Gleixner To: Linus Torvalds Return-path: Received: from moutng.kundenserver.de ([212.227.17.9]:57551 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753918Ab0INVZ2 (ORCPT ); Tue, 14 Sep 2010 17:25:28 -0400 In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Tuesday 14 September 2010 22:53:31 Linus Torvalds wrote: > Oh well. I guess there's no incremental way to do things sanely. And > nobody has patches to fix those users, I guess. The only critical user is fs/lockd, I can easily handle the rest. When I talked to Bruce and Trond during LinuxCon, they told me that it should be possible to separate the bits of fs/lockd that lock against fs/locks.c and convert the former to use lock_flocks(). That would be enough to actually apply this patch without the nasty CONFIG_BKL check and with changes to the few other consumers of file locks. My original plan was to have my current patch in -next until that happens. Arnd