Date: Sat, 26 Nov 2005 12:43:36 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Csaba Henk <csaba-ml@creo.hu> Cc: freebsd-current@freebsd.org, Kris Kennaway <kris@obsecurity.org> Subject: Re: double close strikes panic if md attaching a corrupt file Message-ID: <20051126124248.L81764@fledge.watson.org> In-Reply-To: <20051126054748.GM2911@beastie.creo.hu> References: <20051125214738.GL2911@beastie.creo.hu> <20051126025620.GA62284@xor.obsecurity.org> <20051126054748.GM2911@beastie.creo.hu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 26 Nov 2005, Csaba Henk wrote: > On Fri, Nov 25, 2005 at 09:56:20PM -0500, Kris Kennaway wrote: >>> I attach two patches, they realize the above ideas, respectively. >>> Note that I didn't test either. >> >> You probably should do so ;-) This isn't the easiest thing for someone >> to test without such corrupted media. > > Umm... I was hoping that someone in the list will suggest a way for > easily creating corrupt files. As I don't have a corrupt media, either > :) > > I picked this when Fuse was panicking upon md attaching from a Fuse > based filesystem, cf. > > http://lists.freebsd.org/pipermail/freebsd-ports/2005-November/027724.html Well, a very easy way to test would be to add a local modification to UFS to create a file flag that causes VOP_READ to return EIO :-). That way you can easily mark files to return EIO. Robert N M Watson
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20051126124248.L81764>