fs/befs/ChangeLog
Source file repositories/reference/linux-study-clean/fs/befs/ChangeLog
File Facts
- System
- Linux kernel
- Corpus path
fs/befs/ChangeLog- Extension
[no extension]- Size
- 14364 bytes
- Lines
- 418
- Domain
- Core OS
- Bucket
- VFS And Filesystem Core
- Inferred role
- Core OS: VFS And Filesystem Core
- Status
- atlas-only
Why This File Exists
Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Core operating-system implementation surface: boot, tasks, memory, VFS, syscall-facing interfaces, synchronization, credentials, and isolation.
- Allocates kernel memory; connect allocation flags and lifetime to context constraints.
- Defines or uses C structs; map object ownership, embedded links, reference counts, and lock ownership.
Dependency Surface
- No C-style include directives detected by the generator.
Detected Declarations
- No top-level syscall, struct, function, initcall, or export declaration detected by the generator.
Annotated Snippet
Version 0.92 (2002-03-29)
==========
* Minor cleanup. Ran Lindent on the sources.
Version 0.92 (2002-03-27)
==========
* Fixed module makefile problem. It was not compiling all the correct
source files!
* Removed duplicated function definition
* Fixed potential null pointer dereference when reporting an error
Version 0.91 (2002-03-26)
==========
* Oy! Fixed stupid bug that would cause an unresolved symbol error.
Thanks to Laszlo Boszormenyi for pointing this out to me.
Version 0.9 (2002-03-14)
==========
* Added Sergey S. Kostyliov's patch to eliminate memcpy() overhead
from b+tree operations. Changes the befs_read_datastream() interface.
* Segregated the functions that interface directly with the linux vfs
interface into their own file called linuxvfs.c. [WD]
Version 0.64 (2002-02-07)
==========
* Did the string comparison really right this time (btree.c) [WD]
* Fixed up some places where I assumed that a long int could hold
a pointer value. (btree.c) [WD]
* Andrew Farnham <andrewfarnham@uq.net.au> pointed out that the module
wouldn't work on older (<2.4.10) kernels due to an unresolved symbol.
This is bad, since 2.4.9 is still the current RedHat kernel. I added
a workaround for this problem (compatibility.h) [WD]
* Sergey S. Kostyliov made befs_find_key() use a binary search to find
keys within btree nodes, rather than the linear search we were using
before. (btree.c) [Sergey S. Kostyliov <rathamahata@php4.ru>]
* Made a debian package of the source for use with kernel-package. [WD]
Version 0.63 (2002-01-31)
==========
* Fixed bug in befs_find_brun_indirect() that would result in the wrong
block being read. It was introduced when adding byteswapping in
0.61. (datastream.c) [WD]
* Fixed a longstanding bug in befs_find_key() that would result in it
finding the first key that is a substring of the string it is searching
for. For example, this would cause files in the same directory with
names like file1 and file2 to mysteriously be duplicates of each other
(because they have the same inode number). Many thanks to Pavel Roskin
for reporting this serious bug!!!
(btree.c) [WD]
* Added support for long symlinks, after Axel Dorfler explained up how
they work. I had forgotten all about them. (inode.c, symlink.c) [WD]
* Documentation improvements in source. [WD]
* Makefile fix for independent module when CONFIG_MODVERSION is set in
kernel config [Pavel Roskin <proski@gnu.org>]
* Compile warning fix for namei.c. [Sergey S. Kostyliov <rathamahata@php4.ru>]
Version 0.62
==========
Annotation
- Atlas domain: Core OS / VFS And Filesystem Core.
- Implementation status: atlas-only.
Implementation Notes
- This generated page is the file-by-file coverage layer; curated subsystem chapters should link here when they synthesize a multi-file control flow.
- Core OS pages should be promoted from atlas-only to deep-reviewed when they explain data structures, invariants, locking, lifecycle, and C implementation snippets.
- Driver-family pages are intentionally pattern-oriented unless they are part of the selected PCIe/NVMe representative device path.