Age | Commit message (Collapse) | Author |
|
|
|
This was found thanks to kmalloc now filling new allocations with random
data.
|
|
|
|
This also changes the ext2 filesystem so it will now write to the file
it mounted. Currently the file mounted is /dev/sda which points to a
SATA drive.
|
|
It will now also create a corresponding /dev/sd* device for each
detected SATA drive. The filesystem still writes using the ATA driver.
This should be fixed soon.
|
|
This caused the tables to be cloned instead of having the pointer copied
on the new page directory creations.
This is just a solution to the symptom of having a bad design for
memory managment. Maybe I will figure out something better.
|
|
I would like to be able to free some of those objects but I have not
decided upon how that will be done yet. Even if not freeded the added
complexity of having two functions does not make the extra bytes saved
worth it IMO.
|
|
This is mainly done to test for uninitlalized memory and find bugs
faster. Therefore it does not need to be cryptographically secure or
perfectly uniform. Xoshiro256++ seems like a good fit.
|
|
|
|
|
|
|
|
Currently certain parts of the code are taken from osdev wiki as there
seems to be very little documentation that I can find on how H2D FIS is
structured. Those parts, especially some of the uglier parts of the
example code will be rewritten/changed.
|
|
class
|
|
string
|
|
|
|
This should make it easier to spot uninitalized memory being used.
|
|
|
|
|
|
This commit also changes "unsigned char" to "char". A slight step in the
direction of making my coding style less bipolar.
|
|
This also solves a bug where the data_p pointer could get out of range
due to incorrect assumptions being made about the ext2 directory layout.
To be fair even a faulty ext2 directory layout should not be able to
cause memory bugs.
|
|
|
|
zero.
|
|
The kernel would randomly crash. Turns out I did not zero out the frames
so my page allocator seemed to get into some weird state.
|
|
Previously this would be hardcoded but now it can be detected by the
bootloader and passed in via the multiboot header.
|
|
Previously this would be hardcoded but now it can be detected by the
bootloader and passed in via the multiboot header.
|
|
|
|
|
|
The kernel can now fully compile under O3 without any noticable
problems :)
|
|
If the string is pointed to a very exact location in memory the loop
never finishes.
|
|
|
|
This is to allow both the kernel and the userland to share certain
header files and to make the folder structure a bit more clear.
|