Closed OlliV closed 4 years ago
Something in the reverse lookup is broken because every directly at the root level is shown as boot. E.g. /usr/examples is shown as /boot/examples. This might be caused by a bug in fatfs, and not fs subsystem itself.
boot
/usr/examples
/boot/examples
The issue is that we see .. always as inode 0 for fatfs.
..
and the reason is here: https://github.com/Zeke-OS/zeke/blob/37df35becaeef09b975a763388063882db6bf39c/kern/fs/fatfs/fatfs.c#L883-L885
The ino calculation is not reliable. Sometimes directories get different values depending on if we are doing readdir on . or statting the directory.
.
Something in the reverse lookup is broken because every directly at the root level is shown as
boot
. E.g./usr/examples
is shown as/boot/examples
. This might be caused by a bug in fatfs, and not fs subsystem itself.