mirror of
https://github.com/LadybirdBrowser/ladybird.git
synced 2025-04-26 22:38:51 +00:00
Kernel: Introduce support for using FileSystem object in multiple mounts
The idea is to enable mounting FileSystem objects across multiple mounts in contrast to what happened until now - each mount has its own unique FileSystem object being attached to it. Considering a situation of mounting a block device at 2 different mount points at in system, there were a couple of critical flaws due to how the previous "design" worked: 1. BlockBasedFileSystem(s) that pointed to the same actual device had a separate DiskCache object being attached to them. Because both instances were not synchronized by any means, corruption of the filesystem is most likely achieveable by a simple cache flush of either of the instances. 2. For superblock-oriented filesystems (such as the ext2 filesystem), lack of synchronization between both instances can lead to severe corruption in the superblock, which could render the entire filesystem unusable. 3. Flags of a specific filesystem implementation (for example, with xfs on Linux, one can instruct to mount it with the discard option) must be honored across multiple mounts, to ensure expected behavior against a particular filesystem. This patch put the foundations to start fix the issues mentioned above. However, there are still major issues to solve, so this is only a start.
This commit is contained in:
parent
965afba320
commit
0fd7b688af
Notes:
sideshowbarker
2024-07-17 08:43:11 +09:00
Author: https://github.com/supercomputer7
Commit: 0fd7b688af
Pull-request: https://github.com/SerenityOS/serenity/pull/14932
Issue: https://github.com/SerenityOS/serenity/issues/11283
Reviewed-by: https://github.com/ADKaster ✅
17 changed files with 168 additions and 33 deletions
|
@ -77,9 +77,16 @@ ext2_group_desc const& Ext2FS::group_descriptor(GroupIndex group_index) const
|
|||
return block_group_descriptors()[group_index.value() - 1];
|
||||
}
|
||||
|
||||
ErrorOr<void> Ext2FS::initialize()
|
||||
bool Ext2FS::is_initialized_while_locked()
|
||||
{
|
||||
MutexLocker locker(m_lock);
|
||||
VERIFY(m_lock.is_locked());
|
||||
return !m_root_inode.is_null();
|
||||
}
|
||||
|
||||
ErrorOr<void> Ext2FS::initialize_while_locked()
|
||||
{
|
||||
VERIFY(m_lock.is_locked());
|
||||
VERIFY(!is_initialized_while_locked());
|
||||
|
||||
VERIFY((sizeof(ext2_super_block) % logical_block_size()) == 0);
|
||||
auto super_block_buffer = UserOrKernelBuffer::for_kernel_buffer((u8*)&m_super_block);
|
||||
|
@ -109,7 +116,7 @@ ErrorOr<void> Ext2FS::initialize()
|
|||
set_fragment_size(EXT2_FRAG_SIZE(&super_block));
|
||||
|
||||
// Note: This depends on the block size being available.
|
||||
TRY(BlockBasedFileSystem::initialize());
|
||||
TRY(BlockBasedFileSystem::initialize_while_locked());
|
||||
|
||||
VERIFY(block_size() <= (int)max_block_size);
|
||||
|
||||
|
@ -1680,7 +1687,7 @@ unsigned Ext2FS::free_inode_count() const
|
|||
return super_block().s_free_inodes_count;
|
||||
}
|
||||
|
||||
ErrorOr<void> Ext2FS::prepare_to_unmount()
|
||||
ErrorOr<void> Ext2FS::prepare_to_clear_last_mount()
|
||||
{
|
||||
MutexLocker locker(m_lock);
|
||||
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue