From owner-freebsd-hackers Tue Aug 24 6:15:58 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from karl.tools.de (karl.TooLs.DE [192.76.135.65]) by hub.freebsd.org (Postfix) with ESMTP id 5E21E150D6 for ; Tue, 24 Aug 1999 06:15:37 -0700 (PDT) (envelope-from ws@tools.de) Received: from kurt.tools.de (kurt.TooLs.DE [192.76.135.70]) by karl.tools.de (8.8.8/8.8.8) with SMTP id PAA07880; Tue, 24 Aug 1999 15:15:10 +0200 (MET DST) Received: by kurt.tools.de (SMI-8.6/SMI-SVR4) id PAA22612; Tue, 24 Aug 1999 15:15:09 +0200 Date: Tue, 24 Aug 1999 15:15:09 +0200 From: ws@tools.de (Wolfgang Solfrank) Message-Id: <199908241315.PAA22612@kurt.tools.de> To: bouyer@antioche.lip6.fr Subject: Re: Need some advice regarding portable user IDs Cc: freebsd-hackers@FreeBSD.ORG, tech-userlevel@netbsd.org, tech-kern@netbsd.org X-Sun-Charset: US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Hi, > > What I meant to say was that code of the various filesystems currently > > assumes that the data on the media is somewhat consistent. Since the > > intention is that Joe User can mount some arbitrary floppy (or zip disk, > > or ...), the in kernel filesystem code needs to check any data it > > reads off the media for plausibility. [...] > Solving this is not trivial, I don't think changing the panic() to > return(appropriate_error_code) is the rigth thing to do, in some case > you want to panic if a filesystem gets corrupted. This could probably > be switched on/off for root/non-root mounts. > Also I think there are some cases where it's too late to recover gracefully. Hmm, I think the appropriate thing to do is some equivalent of "panic"ing, but only for the filesystem in question. I.e. something like forcibly unmounting that filesystem (but maybe continue to return EIO on access to anything below the mountpoint?). Whether to flush dirty buffers for the filesystem in question out or not, I'm not sure about either. Ciao, Wolfgang -- ws@TooLs.DE (Wolfgang Solfrank, TooLs GmbH) +49-228-985800 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message