![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to BUGS CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [GPL Stacker compression] / dmsdos|
Return to BUGS CVS log | Up to [GPL Stacker compression] / dmsdos |
1.1 root 1:
2: Known bugs:
3: -----------
4:
5: - Support for 2.3.XX is broken now. It is uder development and is targeted
1.1.1.2 ! root 6: to 2.3.99 and higher. MMAP support for 2.3.XX is untested and MMAP may
! 7: lead to Oops.
! 8:
! 9: - Support for 2.3.XX is broken now. It is uder development and is targeted
1.1 root 10: to 2.3.30 and higher. MMAP support for 2.3.XX is missing and MMAP will
11: lead to Oops.
12:
13: - In some 2.1.XX kernels umsdos support is broken. Get at least 2.1.94
14: if you want to use umsdos-style long filenames in CVFs. For 2.0.xx
15: and 2.2.x kernels everything is okay.
16:
17: - Advanced memory allocation (XMALLOC) may crash a 2.1.xx/2.2.xx system.
18: I once got a report of a serious crash with old dmsdosfs. The code
19: for XMALLOC has never been changed, but the kernel keeps changing...
20: It is known to work without problems under 2.0.xx.
21:
22: - Writable mmap support must be turned *on* for newer 2.1.xx and all 2.2.xx
23: kernels. The code fails to compile if it is switched off, so you'll see it
24: quite early :)
25:
26: - Mounting with the cvf_format=xxx mount option may succeed even if the
27: specified format xxx is not present. The CVF-FAT interface does auto-
28: detection if an invalid format is specified. This was meant as a feature
29: but seems to cause confusion. In rare cases it may lead to a CVF accessed
30: by the plain FAT driver (which does not complain on mount but it will
31: scream loudly when, for example, a 'ls' is done on the mount point).
32: This bug is fixed by updating the file cvf.c as described in INSTALL.TXT.
33:
34:
35: Kernel bugs related to using dmsdos
36: -----------------------------------
37:
38: - vfat brelse bug
39: Priority: Serious.
40: Affected kernels: 2.2.0, 2.2.1, 2.2.2, probably late 2.1.xx.
41: Fixed since: --not yet fixed, hopefully fixed in 2.2.3 or 2.2.4--
42: Symptom: Kernel panics with "VFS: LRU list corrupted" and hangs.
43: Fix: See file patches/DIFFS.TXT for a patch.
44:
45: - fat truncate bug
46: Priority: Minor.
47: Affected kernels: all 2.0.xx, all 2.1.xx, 2.2.0, 2.2.1, 2.2.2.
48: Fixed since: --not yet fixed, hopefully fixed in 2.2.3 or 2.2.4--
49: Symptom: Kernel can write to read-only mounted CVF and corrupt the FAT.
50: Happens very rarely and requires a slightly damaged filesystem
51: to provoke this bug.
52: Fix: See file patches/DIFFS.TXT for a patch.
53:
54: - msdos rmdir bug
55: Priority: Minor.
56: Affected kernels: 2.0.34, 2.0.35, FAT32-patched 2.0.33 or earlier,
57: some 2.1.xx (unknown which ones)
58: Fixed since: 2.0.36, unknown for 2.1.xx
59: Symptom: Removing non-empty directories succeeds but leaves lost cluster
60: chains behind.
61: Fix: See file patches/DIFFS.TXT for a patch.
62:
63: - fat add cluster / fat extend dir for 2.3.xx
64: Priority: Serious.
1.1.1.2 ! root 65: Affected kernels: 2.2.?-2.2.13+, all 2.3.xx
1.1 root 66: Fixed since: --not yet fixed, hopefully fixed in 2.2.15 and 2.3.31--
1.1.1.2 ! root 67: Symptom: File or directory (only dir for 2.3.x) cannot be enlarged.
1.1 root 68: Fix: See file patches/DIFFS.TXT for a patch.
69:
70: - fat read super
71: Priority: Serious.
1.1.1.2 ! root 72: Affected kernels: all 2.3.xx
1.1 root 73: Fixed since: --not yet fixed, hopefully fixed in 2.3.31--
74: Symptom: Oops during CVF mount phase.
75: Fix: See file patches/DIFFS.TXT for a patch.
76:
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.