Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 15 Mar 2003 11:19:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 15 Mar 2003 11:19:44 -0500 Received: from comtv.ru ([217.10.32.4]:38056 "EHLO comtv.ru") by vger.kernel.org with ESMTP id ; Sat, 15 Mar 2003 11:19:43 -0500 X-Comment-To: Andrew Morton To: Andrew Morton Cc: bzzz@tmi.comex.ru, linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net Subject: Re: [PATCH] remove BKL from ext2's readdir References: <20030315023614.3e28e67b.akpm@digeo.com> <20030315030322.792fa598.akpm@digeo.com> From: Alex Tomas Organization: HOME Date: 15 Mar 2003 19:22:23 +0300 In-Reply-To: <20030315030322.792fa598.akpm@digeo.com> Message-ID: User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 682 Lines: 10 >>>>> Andrew Morton (AM) writes: AM> hm, no. lseek is using the directory's i_sem now, and readdir AM> runs under that too. So we should be able to remove AM> lock_kernel() from the readdir implementation of all filesystems AM> which are using generic_file_llseek(). looks like only coda and ntfs use generic_file_llseek(). other use default_llseek(). what's the reason do not use generic_file_llseek(). historical only? or not? - 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/