users

users@lists.genode.org

9 participants
2316 discussions

Region Map's Permission Difficulties
by Rumen Mitov 25 Jul '25

25 Jul '25

Hi, I have been having some trouble with the Region Map interface not setting the correct permissions in my specified memory region. I am trying to replicate a similar functionality to rm_nested: ```cpp const addr_t OBJECT_SPACE_START = 0x80000000; const addr_t OBJECT_SPACE_SIZE = 0x40000000; Genode::Env &_env; Genode::Rm_connection _rm{_env}; // To be attached to env's rm Genode::Region_map_client _obj_space{_rm.create(OBJECT_SPACE_SIZE)}; ... Region_map::Attr attributes{.size = OBJECT_SPACE_SIZE, .offset = 0, .use_at = true, .at = OBJECT_SPACE_START, .executable = true, .writeable = true}; addr_t ptr_obj = 0; env.rm() .attach(_obj_space.dataspace(), attributes) .with_result( [&ptr_obj](Genode::Env::Local_rm::Attachment &attachment) { ptr_obj = (Genode::addr_t)attachment.ptr; attachment.deallocate = false; }, [](auto) { error("couldn't attach dataspace!"); throw; }); ``` I expect this code snippet to make the region at 0x80000000 to be rwx, however when I run my program with GDB I see that the permissions are ---p: (gdb) info proc mappings Mapped address spaces: Start Addr End Addr Size Offset Perms objfile 0x80000000 0xc0000000 0x40000000 0x0 ---p I have also tried adding a dataspace capability to _obj_space ( before attaching it to env.rm() ) but that had no effect on the permissions: ```cpp _obj_space.attach(env.ram().alloc(OBJECT_SPACE_SIZE), attributes); ``` Any help / suggestions would be greatly appreciated as I have been stuck on this for quite a while! Best, Rumen P.S. The permissions are set correctly when I do: ```cpp addr_t ptr_obj = 0; env.rm() .attach(env.ram().alloc(OBJECT_SPACE_SIZE), attributes) .with_result( [&ptr_obj](Genode::Env::Local_rm::Attachment &attachment) { ptr_obj = (Genode::addr_t)attachment.ptr; attachment.deallocate = false; }, [](auto) { error("couldn't attach dataspace!"); throw; }); ``` The problem with this is that later on in my program I get an error as I need the _obj_space region map client.

2 3

GUI Incompatible with Genode 25.05?
by Rumen Mitov 17 Jul '25

17 Jul '25

Hi, I am trying to port an old Genode project (uses Genode 24.02) to Genode 25.05. The problem is that I get build errors due to the fact that genodelabs/api/base/2025-04-09 uses a newer interface for some functions which have not been updated for genodelabs/api/gui_session/2024-10-29 (see the log file for more details). I checked https://depot.genode.org/ and the latest gui_session depot version is 2024-10-29. What is the timeframe of updating the gui_session to Genode 25.05? I would like to know if it is worth the effort of porting the project to a less recent version of Genode (e.g. 24.10) or if I should just wait for the update. Best, Rumen

2 1

Using the Lwext4 Project with Goa
by Rumen Mitov 16 Jul '25

16 Jul '25

Hello, I have managed to integrate the lwext4 Genode port (https://codeberg.org/jws/genode-wundertuete/src/branch/sculpt-25.04-2025-04…) in the past with the target.mk approach. However, recently I have changed my build system to Goa with CMake. From what I understand the only thing I need to add to my build configuration is the path to `<lwext4-repo>/recipes/src/vfs_lwext4` (for reference: https://codeberg.org/jws/genode-wundertuete/src/branch/sculpt-25.04-2025-04…). Unfortunately, when I try adding the aforementioned path in my `<project>/pkg/<project>/archives` file, I get the following error: "Error: invalid depot-archive path '_/_/_/wundertuete/recipes/src/vfs_lwext4'". Could someone kindly let me if I am missing or misunderstood something? I do not need the lwext4 library itself, only the integration of it into the VFS. Best, Rumen

2 5

vfs_block Persistence
by Rumen Mitov 16 Jul '25

16 Jul '25

Hi, I wanted to ask about the new vfs_block and how a block file can be made persistent between Goa runs. My vfs_block configuration is as follows: <content> <rom label="vfs"/> <rom label="vfs_block"/> <rom label="vfs.lib.so"/> <rom label="vfs_import.lib.so"/> <rom label="vfs_lwext4.lib.so" /> <rom label="snapper_block.raw"/> </content> <start name="vfs_block" ram="1G"> <provides><service name="Block"/></provides> <config> <vfs> <ram/> <import> <rom name="snapper_block.raw"/> </import> </vfs> <policy label_prefix="vfs" file="/snapper_block.raw" block_size="512" writeable="yes"/> </config> </start> My program runs successfully, however changes made to the block file (snapper_block.raw) do not persist. This is because I use <ram/>. But without <ram/> I get an error that the block file is inaccessible. How can I make the block changes persist between runs? In previous versions of Genode I could achieve this with lx_block, but I am unsure how to do this with vfs_block. Best, Rumen

2 2

vfs plugin per-client RAM quota
by Stefan Thöni 08 Jul '25

08 Jul '25

Dear Genodians One of our vfs plugins needs a bit more RAM per client. Therefore the question came up, if RAM quota donation from the client is supported for vfs plugins and if so where one might find an example of this mechanism. Best regards Stefan

2 1

Determine total resources consumed within a nested init
by Sid Hussmann 04 Jul '25

04 Jul '25

Dear Genodians, I want to determine the total resources consumed within a deeply nested subsystem. The only apparent way to do this is to iterate through all the init state reports of the children and their ancestors down to the leaf and accumulate the respective `ram_used` and `caps_used` attributes of the `child` nodes. Is this the way? Intuitively, the parent at the tree's root should be aware of this information. However, after digging through the documentation and the code, I found that this `total_ram_used`/`total_caps_used` information is not available out of the box within an init component/sandbox library. I assume the reason for this is that there is no (easy) way to communicate this information all the way back to the parent. On the other hand, implementing a monitor component that goes through all these recursive init state reports, not knowing how deep the tree is, and assuming that all the sub-inits correctly report their state seems quite error-prone. Is my assumption correct that the only way to determine a subsystem's resource consumption is to aggregate the init state reports down to the leaf? Cheers, Sid -- Sid Hussmann CTO & Founder Gapfruit AG Baarerstrasse 135 6300 Zug - Switzerland sid.hussmann(a)gapfruit.com https://gapfruit.com

2 2

The new MNT Reform (RK3588)
by Michael Grunditz 04 Jul '25

04 Jul '25

Hi! Are there any plans for supporting the new MNT Reform's SoC? If so , I might be able to help. BR Michael Grunditz

1 0

Announcement: Genode OS Framework version 25.05 released
by Christian Helmuth 28 May '25

28 May '25

Hello everyone, I'm happy to announce the May 2025 release of Genode. https://genode.org/documentation/release-notes/25.05 According to this year's motto "rigidity, clarity, and performance", the Genode 25.05 release focuses on API safety, consolidation work, and developer tooling.The most prominent change in this release is the much revised framework API that no longer relies on the C++ exception mechanism but precisely encodes all possible error conditions as sum types, an inspiration taken from the Rust-language community. This approach rules out several classes of programming errors by design and, thus, enforces the conscious handling of error conditions, eliminates the accidental leakage of pointers, as well as promotes clarity of object ownership and lifetimes. The fair amount of consolidation work in the this release includes, for example, the unified integration of the Linux and lwIP TCP/IP stacks paving the ground for subsequent network-protocol improvements and optimizations. Feature-wise, we add a new VFS plugin for generating pseudo random numbers, support for touch gestures, and display rotation and flipping on Intel hardware. Also following our biennial update routine, we use a recent tool chain based on GCC 14.2, binutils 2.44, and GDB 16.3 starting with this release for the next 24 months. Further, the Goa SDK now mitigates security risks while importing, building, and testing projects of unvetted origin by sandboxing all tools and tightly restricting the reach of its own configuration files. The current release contains the following changes and new features: - Tool chain upgraded to GCC 14.2 and binutils 2.44 - Hardened API, leveraging sum types for error handling - Security-enhanced Goa SDK - New support for touch gestures - New VFS plugin for generating pseudo random numbers - Revisited integration of the Linux and lwIP TCP/IP stacks - Display rotation and flipping on Intel hardware - Dynamic mode switching and reporting of the VESA display driver Read the complete release documentation for the version 25.05 here https://genode.org/documentation/release-notes/25.05 Best regards -- Christian Helmuth Genode Labs https://www.genode-labs.com/ · https://genode.org/ https://floss.social/@genode · https://genodians.org/ https://de.linkedin.com/company/genodelabs Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

laptop boots fine into 25.04
by Guido 16 May '25

16 May '25

Hi Genodians, At the Hack-n-Hike, I ran into a boot loop after upgrading Sculpt 24.10 to 25.04. However, when I test with a fresh 25.04 image from the website (sha256: 54e8bd...), the very same laptop boots OK. However, I do run into an issue when I upgrade from 24.10 to 25.04 but I'll investigate first before reporting or requesting help. Thanks for the wonderful HnH. Cheers, Guido.

2 2

Extending the VFS with hard-links
by Rumen Mitov 02 May '25

02 May '25

Hello, I need some help with extending the VFS for my project. I need hardlink support, so I added the following to repos/os/include/vfs/directory_service.h's Directory_service struct: virtual int hardlink(char const *path, char const *hardlink_path) { (void) path; (void)hardlink_path; Genode::error("not implemented!"); return 0; } I have the Lwext4 plugin (https://codeberg.org/jws/genode-wundertuete/src/branch/import-lwext4_from_w…) setup for my project so I then extended repos/wundertuete/src/lib/vfs/lwext4/vfs.cc's Lwext4_vfs_file_system struct: int hardlink(char const *path, char const *hardlink_path) override { return ext4_flink(path, hardlink_path); } The problem is that hardlink uses the default implementation in my main code: squidutils->_vfs_env.root_dir().hardlink(p2.string(), p1.string()); // Prints 'not implemented' From what I have read online the issue is that squidutils->_vfs_env.root_dir() is of type Directory_service, whereas I need it to be Lwext4_vfs_file_system. However, Lwext4_vfs_file_system is declared in the vfs.cc file above as opposed to being declared in a header. Is there a way to use Lwext4_vfs_file_system without copying the entire source of Lwext4 into my project's source code? Or am I perhaps going in the wrong direction with all of this? Best, Rumen

4 4

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users