simplefs
simplefs copied to clipboard
sysprog21
A simple native file system for Linux kernel
It works until kernel 5.18. But I can not compile this with kernel 5.19. Did I miss any CONFIGS? ``` file.c:86:12: error: implicit declaration of function ‘mpage_readpage’; did you mean...
function simplefs_create() miss check whether eblock->nr_files bigger than SIMPLEFS_MAX_SUBFILES so when eblock->nr_files is large, ``eblock->extents[ei].ee_start `` will cause array out of bounds problem ```c static int simplefs_create(struct inode* dir, struct...
file : mkfs.c fucntion: write_bfree_blocks line : bfree[i] = htole64(line) block arr is out of bounds.
As I followed the `Build and Run` section to test the mounted file system. The two directories `.` and `..` didn't show correctly. ### Step to reproduced ``` $ sudo...
Use `make check` to reproduce. Reported by `dmesg`: ``` Bad or missing usercopy whitelist? Kernel memory exposure attempt detected from SLUB object 'simplefs_cache' (offset 4, size 4)! Call Trace: __check_heap_object+0xb7/0x120...
I was wandering on your GitHub profile after reading the LKMPG book and found it useful. I see that this is another, similar effort, but for VFS. I'm wondering if...
Originally implemented in ext3, the ext4 filesystem utilizes a journal to safeguard against metadata inconsistencies following a system crash. While [the earlier version of simplefs](https://github.com/psankar/simplefs/commits/master/) (`journal-v6` branch) supported journaling through...
This PR addressed issue #50 , but I don't think I fully understand the reason why that if we not initial the disk to zero, it will cause error happended.
If I fill the image with `/dev/random`, command `touch` or `mkdir` will error ``` $ dd if=/dev/random of=test.img bs=1M count=32 ``` and then ``` $ touch test.txt ``` the error...
Using kmemleak to detect the leak, I found the the command "ls" and "mv" will make the cache leak here are the leak informations: 0 [] __alloc_pages+0x24e 1 [] __alloc_pages+0x24e...
