From: "Stephen C. Tweedie" <sct@redhat.com> To: Daniel Phillips <phillips@bonn-fries.net> Subject: Re: ext3-2.4-0.9.4 Date: Fri, 3 Aug 2001 10:06:33 +0100 Cc: Matthias Andree <matthias.andree@stud.uni-dortmund.de>, "Stephen C. Tweedie" <sct@redhat.com>, linux-kernel@vger.kernel.org Hi, On Thu, Aug 02, 2001 at 07:26:16PM +0200, Daniel Phillips wrote: > I believed you've summarized the SUS requirements very well. Apart > from legalistic arguments, Umm, this is a specification. It is *supposed* to be interpreted legalistically! > SUS quite clearly states that fsync should > not return until you are sure of having recorded not only the file's > data, but the access path to it. I interpret this as being able to > "access the file by its name", and being able to guess by looking in > lost+found doesn't count. But that is just an interpretation. There's nothing in the spec which forces that interpretation. fsync forces the data to disk. There may be one or more pathnames which the application also relies on, and if the application does care about those, the application will have to ensure that they are synced too. Look, I agree that your interpretation is useful. It's just not an unambiguous requirement of the spec. Cheers, Stephen - 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/