i2p/haiku-beta6
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

ramfs: Do not advertise ourselves as a persistent filesystem.

Browse Source 
The original change to fix ramfs appearance (hrev56642)
in Tracker and elsewhere said the reason for adding the
FS_IS_REMOVABLE flag instead of removing FS_IS_PERSISTENT
was because of problems encountered with writing/deleting
entries on ramfs mounts.

I was unable to reproduce those problems; writing and
deleting entries on RAMFS mounts still works just fine
in Tracker and elsewhere, even after removing the flag.
So it seems safe to remove; subsequent problems can be
addressed as they come up.

Fixes #18173.
This commit is contained in:
Augustin Cavalier
2023-08-24 21:02:30 -04:00
parent 4e145eadc6
commit 4024e5b6a4
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
src/add-ons/kernel/file_systems/ramfs/kernel_interface.cpp
+2 -2
View File
@@ -138,8 +138,8 @@ ramfs_read_fs_info(fs_volume* _volume, struct fs_info *info)
Volume* volume = (Volume*)_volume->private_volume;
status_t error = B_OK;
if (VolumeReadLocker locker = volume) {
info->flags = B_FS_IS_PERSISTENT | B_FS_HAS_ATTR | B_FS_HAS_MIME
| B_FS_HAS_QUERY | B_FS_IS_REMOVABLE;
info->flags = B_FS_HAS_ATTR | B_FS_HAS_MIME | B_FS_HAS_QUERY
| B_FS_IS_REMOVABLE;
info->block_size = B_PAGE_SIZE;
info->io_size = kOptimalIOSize;
info->total_blocks = volume->CountBlocks();