From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268217AbUHFRGS (ORCPT ); Fri, 6 Aug 2004 13:06:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266013AbUHFRCl (ORCPT ); Fri, 6 Aug 2004 13:02:41 -0400 Received: from anchor-post-30.mail.demon.net ([194.217.242.88]:24075 "EHLO anchor-post-30.mail.demon.net") by vger.kernel.org with ESMTP id S268207AbUHFQ7H (ORCPT ); Fri, 6 Aug 2004 12:59:07 -0400 Message-ID: <4113B8A2.4050609@lougher.demon.co.uk> Date: Fri, 06 Aug 2004 17:58:10 +0100 From: Phillip Lougher User-Agent: Mozilla/5.0 (X11; U; Linux ppc; en-GB; rv:1.2.1) Gecko/20030228 X-Accept-Language: en, en-us MIME-Version: 1.0 To: Nick Piggin CC: linux-kernel@vger.kernel.org, Andrew Morton , viro@parcelfarce.linux.theplanet.co.uk Subject: Re: [PATCH] VFS readahead bug in 2.6.8-rc[1-3] References: <41127371.1000603@lougher.demon.co.uk> <4112D6FD.4030707@yahoo.com.au> <4112EAAB.8040005@yahoo.com.au> In-Reply-To: <4112EAAB.8040005@yahoo.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Nick Piggin wrote: > On second thought, maybe not. I think your filesystem is at fault. No I'm not wrong here. With a read-only filesystem i_size can never change, there are no possible race conditions. If a too large index is passed it is a VFS bug. Are you suggesting I should start to code assuming the VFS is broken?