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