From owner-freebsd-fs@FreeBSD.ORG Mon Sep 19 00:12:42 2005 Return-Path: X-Original-To: freebsd-fs@freebsd.org Delivered-To: freebsd-fs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DED7316A41F for ; Mon, 19 Sep 2005 00:12:42 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6EAF043D46 for ; Mon, 19 Sep 2005 00:12:39 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id j8J0CScX021752; Sun, 18 Sep 2005 18:12:29 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <432E0274.4010704@samsco.org> Date: Sun, 18 Sep 2005 18:12:36 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050615 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <20050918235724.GA67621@xor.obsecurity.org> <200509190000.j8J0046l014890@agora.fsl.cs.sunysb.edu> <20050919000134.GA67976@xor.obsecurity.org> In-Reply-To: <20050919000134.GA67976@xor.obsecurity.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org Cc: freebsd-fs@freebsd.org, Erez Zadok , christos@zoulas.com Subject: Re: turning off the NFS attribute cache X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Sep 2005 00:12:43 -0000 Kris Kennaway wrote: > On Sun, Sep 18, 2005 at 08:00:04PM -0400, Erez Zadok wrote: > >>In message <20050918235724.GA67621@xor.obsecurity.org>, Kris Kennaway writes: >> >>>Thanks for clarifying...6.0 is unlikely to have fixed this. >>> >>>Kris >> >>Is 6.0 frozen enough that it's unlikely to be fixed in 6.0? > > > At this point, maybe. If someone can come up with a simple fix quick > enough there might be some chance though. > > Kris There are about 2 more weeks before the window closes on fixing this, assuming that whatever fix is to be had is fairly simple and non-disruptive. Scott