cvs commit: src/sys/fs/msdosfs msdosfs_denode.c

[Mike Silbersack]

On Thu, 8 Sep 2005, Dmitry Pryanishnikov wrote:

> I've thought about it too ;)
>
> Actually, to trigger this error one should have little more than 4Gb device,
> but carefully placed directory on it ;) If we have 2 files, which directory
> entries begin at byte offsets from the start of the media with identical 
> low-order 32 bits; e.g., 64-bit offsets
>
> 0x0000000000001000 and
> 0x0000000100001000

Hm, maybe it wouldn't be too difficult to create, then.  There is an 
option to have compressed filesystems, so if one wrote a huge filesystem 
with files that all contained zeros, perhaps it would compress well 
enough.

If you just started creating a lot of equally sized files containing zero 
as their content, maybe it could be done via a script.  Yeah, you could 
just call truncate in some sort of shell script loop until you have enough 
files, then go back and try reading file "000001", and that should cause 
the panic, right?

Mike "Silby" Silbersack