From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Charles P. Wright" Subject: Re: Expected getdents behaviour Date: Thu, 15 Sep 2005 17:15:36 -0400 Message-ID: <1126818936.23958.2.camel@polarbear.fsl.cs.sunysb.edu> References: <1126793268.1676.9.camel@imp.csi.cam.ac.uk> <1126793558.1676.15.camel@imp.csi.cam.ac.uk> <1126797460.1676.23.camel@imp.csi.cam.ac.uk> <20050915164110.GA25573@hasse.suse.de> <20050915174658.GA9974@wohnheim.fh-wedel.de> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Cc: aaranya@cs.sunysb.edu, linux-fsdevel@vger.kernel.org Return-path: Received: from filer.fsl.cs.sunysb.edu ([130.245.126.2]:21682 "EHLO filer.fsl.cs.sunysb.edu") by vger.kernel.org with ESMTP id S1030506AbVIOVPy (ORCPT ); Thu, 15 Sep 2005 17:15:54 -0400 To: Anton Altaparmakov In-Reply-To: Sender: linux-fsdevel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Thu, 2005-09-15 at 22:00 +0100, Anton Altaparmakov wrote: > The only problem again is when the reference to the > directory entry will be released in the case that no further readdir and > no close ever comes. It causes the fs to be unmountable for example > and the file belonging to the directory entry to be undeletable... Anton, If no further readdir "ever" comes, and the file is never closed, the file system will not be unmountable to begin with. It is just like opening and never closing a normal file, you keep the file system busy. I don't see the connection between the extra per-open-file state you need to save, and the argument that this opens up up for a DoS. Charles