users

users@lists.genode.org

2285 discussions

Sporadic Invalid_clear exception in init
by Pirmin Duss 26 Feb '21

26 Feb '21

Hello Genodians We have a complex scenario in which we deploy 6 configs periodically. The configurations are applied in a loop always in the same order. Eventually init throws 'Genode::Bit_array_base::Invalid_clear' and terminates (see the backtrace below). Maybe it is noteworthy that packages with sub inits that have components that use resource saturation are started. Does anybody have an idea on how to proceed with debugging the problem? Best regards, Pirmin ``` #0 0x0000000050086294 in Genode::Bit_array_base::_set (this=0x50137868 <(anonymous namespace)::local_capability_space()::capability_space+229384>, index=<error reading variable: That operation is not available on integers of more than 8 bytes.>, width=1, free=true) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/bit_array.h:87 #1 Genode::Bit_array_base::_set (free=true, width=1, index=<error reading variable: That operation is not available on integers of more than 8 bytes.>, this=0x50137868 <(anonymous namespace)::local_capability_space()::capability_space+229384>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/bit_array.h:75 #2 Genode::Bit_array_base::clear (width=1, index=<error reading variable: That operation is not available on integers of more than 8 bytes.>, this=0x50137868 <(anonymous namespace)::local_capability_space()::capability_space+229384>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/bit_array.h:149 #3 Genode::Bit_allocator<4096u>::free (num_log2=0, bit_start=<error reading variable: That operation is not available on integers of more than 8 bytes.>, this=0x50137860 <(anonymous namespace)::local_capability_space()::capability_space+229376>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/bit_allocator.h:118 #4 Genode::Capability_space_tpl<4096u, Genode::Native_capability::Data>::dec_ref (data=..., this=0x500ff860 <(anonymous namespace)::local_capability_space()::capability_space>) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/include/base/internal/capability_space_tpl.h:196 #5 Genode::Capability_space::dec_ref (data=...) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/capability_space.cc:63 #6 0x000000005002756f in Genode::Native_capability::~Native_capability (this=0x401ff518, __in_chrg=<optimized out>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/native_capability.h:76 #7 Genode::Capability<Genode::Pd_session>::~Capability (this=0x401ff518, __in_chrg=<optimized out>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/capability.h:53 #8 Genode::Quota_transfer<Genode::Pd_session, Genode::Ram_quota>::Remote_account::~Remote_account (this=0x401ff510, __in_chrg=<optimized out>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/quota_transfer.h:86 #9 Genode::Child::_revert_quota_and_destroy (this=<optimized out>, session=...) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/child.cc:392 #10 0x000000005002800a in Genode::Child::session_closed (this=0x7ffff7f9eed0, session=...) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/child.cc:508 #11 0x0000000050029e99 in Genode::Child::<lambda(Genode::Session_state&)>::operator()(Genode::Session_state &) (session=..., __closure=<optimized out>, __closure=<optimized out>) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/child.cc:532 #12 0x000000005002a3d7 in Genode::Id_space<Genode::Parent::Server>::apply<Genode::Session_state, Genode::Child::session_response(Genode::Parent::Server::Id, Genode::Parent::Session_response)::<lambda(Genode::Session_state&)> > (fn=..., id=..., this=0x7ffff7f96088) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/mutex.h:64 #13 Genode::Child::session_response (this=<optimized out>, id=..., response=<optimized out>) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/child.cc:518 #14 0x000000005003e41d in Genode::Meta::call_member<Genode::Meta::Empty, Genode::Parent, Genode::Meta::Pod_tuple<Genode::Id_space<Genode::Parent::Server>::Id, Genode::Meta::Pod_tuple<Genode::Parent::Session_response, Genode::Meta::Empty> > > (func=<optimized out>, args=<synthetic pointer>..., server=...) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/meta.h:490 #15 Genode::Parent::Rpc_session_response::serve<Genode::Parent, Genode::Meta::Empty> (args=<synthetic pointer>..., server=...) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/parent/parent.h:325 #16 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_serve<Genode::Parent::Rpc_session_response> (args=<synthetic pointer>..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:146 #17 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:180 #18 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #19 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #20 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_session_cap, Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #21 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_session, Genode::Parent::Rpc_session_cap, Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (this=this@entry=0x7ffff7f96318, opcode=..., opcode@entry=..., in=..., out=...) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #22 0x000000005003ef50 in Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_session_sigh, Genode::Parent::Rpc_session, Genode::Parent::Rpc_session_cap, Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/util/meta.h:626 #23 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_announce, Genode::Parent::Rpc_session_sigh, Genode::Parent::Rpc_session, Genode::Parent::Rpc_session_cap, Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #24 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::_do_dispatch<Genode::Meta::Type_list<Genode::Parent::Rpc_exit, Genode::Parent::Rpc_announce, Genode::Parent::Rpc_session_sigh, Genode::Parent::Rpc_session, Genode::Parent::Rpc_session_cap, Genode::Parent::Rpc_upgrade, Genode::Parent::Rpc_close, Genode::Parent::Rpc_session_response, Genode::Parent::Rpc_main_thread, Genode::Parent::Rpc_deliver_session_cap, Genode::Parent::Rpc_resource_avail_sigh, Genode::Parent::Rpc_resource_request, Genode::Parent::Rpc_yield_sigh, Genode::Parent::Rpc_yield_request, Genode::Parent::Rpc_yield_response, Genode::Parent::Rpc_heartbeat_sigh, Genode::Parent::Rpc_heartbeat_response> > (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:201 #25 Genode::Rpc_dispatcher<Genode::Parent, Genode::Parent>::dispatch (out=..., in=..., opcode=..., this=0x7ffff7f96318) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:235 #26 Genode::Rpc_object<Genode::Parent, Genode::Parent>::dispatch (this=0x7ffff7f96290, opcode=..., in=..., out=...) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/rpc_server.h:272 #27 0x000000005006b38a in Genode::Rpc_entrypoint::<lambda(Genode::Rpc_object_base*)>::operator() (obj=0x7ffff7f96290, __closure=<synthetic pointer>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/mutex.h:64 #28 Genode::Object_pool<Genode::Rpc_object_base>::apply<Genode::Rpc_entrypoint::entry()::<lambda(Genode::Rpc_object_base*)> > (func=..., capid=<optimized out>, this=0x500fca50 <Genode::bootstrap_component()::startup+528>) at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/object_pool.h:147 #29 Genode::Rpc_entrypoint::entry (this=0x500fc9a8 <Genode::bootstrap_component()::startup+360>) at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/base/rpc_dispatch_loop.cc:68 #30 0x000000005009ec3d in Genode::Thread::_thread_start () at /data/genode/depot/trimpim/api/base/2021-02-23T1255/include/base/output.h:54 #31 0x00000000500b3e3b in thread_start () at /data/genode/depot/trimpim/src/base-linux/2021-02-23T1255/src/lib/syscall/spec/x86_64/lx_clone.S:62 ```

2 2

RPC Interface for I2C Driver
by Jean-Adrien Domage 25 Feb '21

25 Feb '21

Dear Genodians, We would like to introduce an i2c driver for imx8q_evk to Genode. Thanks to the hints from Sebastian, I now have a prototype component that can send/receive data via the i2c bus of the imx8q_evk. The next task is to design the RPC interface for the driver. What would be a good kind of interface? Do you have driver(s)/component(s) to recommend as example? Or any specific guidelines? Cheers, Jean-Adrien Domage Software Engineer gapfruit AG

3 2

Running Genode on a server system
by Joerg-C. Boehme 25 Feb '21

25 Feb '21

Hi everyone, I like to "use" Genode to get more familiar with it. My idea was to run a Genode server with lighttpd like genodians.org I have a small "Cloud Server" or "vServer" from Hetzner. It looks like they use qemu but unfortunately they use the "440FX" as emulation. It is not possible to use a nic_drv on it [1]. My question is, does somebody know who provide servers where I can install/run a Genode ? I assume the genodians.org is installed on its own hardware and "use a colocation" contract. Btw. I think this is the correct site [2] to see on which hardware genode is running, or? Thanks, Jörg [1] See my email on 24. Feb. 2021 15:01:26 CET: "acpi_drv / platform_drv support" [2] https://usr.sysret.de/jws/genode/hcl.html

1 0

acpi_drv / platform_drv support
by Joerg-C. Boehme 25 Feb '21

25 Feb '21

Hi everyone, I have some question about the: acpi_drv and platform_drv. In short: Is acpi_drv and platform_drv are only supporting hardware boards with PCIe ? In detail: I do following: make KERNEL=nova run/lighttpd And start the var/run/lighttpd.iso with qemu-system-x86_64 (without -machine q35 parameter!) qemu-system-x86_64 -no-kvm -display sdl -cpu core2duo -nographic -netdev user,id=net0,hostfwd=tcp::5555-:80,hostfwd=tcp::5556-:443 -net nic,model=e1000,netdev=net0 -serial mon:stdio -m 512 -cdrom var/run/lighttpd.iso It fails with: .... [init -> nic_drv -> acpi_drv] SMBIOS table (entry point: 0x1758f0 structures: 0xf5910) [init -> nic_drv -> platform_drv] Error: ACPI report parsing error. [init -> nic_drv -> platform_drv] Error: Uncaught exception of type 'int' [init -> nic_drv -> platform_drv] Warning: abort called - thread: ep I extendend the "error output" (maybe you would like to have this? I can create a PR?) And I got following: ... [init -> nic_drv -> acpi_drv] Freeing up memory of elements - 3104 bytes [init -> nic_drv -> acpi_drv] SMBIOS table (entry point: 0x1758f0 structures: 0xf5910) [init -> nic_drv -> platform_drv] Error: ACPI report parsing error. Exception type int: 2 [init -> nic_drv -> platform_drv] Error: ACPI ROM: <acpi> [init -> nic_drv -> platform_drv] <root_bridge bdf="0x0"/> [init -> nic_drv -> platform_drv] <irq_override irq="11" gsi="11" flags="0xd"/> [init -> nic_drv -> platform_drv] <irq_override irq="10" gsi="10" flags="0xd"/> [init -> nic_drv -> platform_drv] <irq_override irq="9" gsi="9" flags="0xd"/> [init -> nic_drv -> platform_drv] <irq_override irq="5" gsi="5" flags="0xd"/> [init -> nic_drv -> platform_drv] <irq_override irq="0" gsi="2" flags="0x0"/> [init -> nic_drv -> platform_drv] </acpi> [init -> nic_drv -> platform_drv] [init -> nic_drv -> platform_drv] Error: Uncaught exception of type 'int' [init -> nic_drv -> platform_drv] Warning: abort called - thread: ep I figured out that following is missing: [init -> nic_drv -> platform_drv] <bdf start="0" count="65536" base="0xb0000000"/> The acpi_drv get this from [init -> nic_drv -> acpi_drv] MCFG BASE 0xb0000000 seg 0x0 bus 0x0-0xff MCFG -> PCI Express memory mapped configuration space base address Description Table I also figured out that the qemu parameter -machine q35 is using as chipset a ICH9 and this has PCIe * Can I somehow "manuel" configure the system on 440FX based hardware ? * Is there a reason why platform_drv is not supporting older hardware ? Thanks Jörg

2 2

Announcement: Genode OS Framework version 21.02 released
by Norman Feske 25 Feb '21

25 Feb '21

I am very happy to announce the release of Genode 21.02, which features the results of three long-term developments. First, it introduces the ability to start, re-start, remove, and update network device drivers at runtime, following the approach we already took for framebuffer and input drivers last year. With this architectural change, the liveliness of network-application stacks no longer depends on the robustness of the used network drivers. Second, the release brings a long anticipated update of VirtualBox. The addition of VirtualBox 6 is not merely an evolutionary update of our aging VirtualBox 5 version. Instead, we repeated the legwork of porting this complex software stack from the ground up, drawing from the many lessons learned since our initial port of VirtualBox 4 in 2014, and refining Genode's virtualization interfaces along the way. The initial version of VirtualBox 6 should nevertheless be regarded as a snapshot of our ongoing development, not as a drop-in replacement of VirtualBox 5, yet. Third, Genode has now became able to use mobile-data connectivity over LTE. The work on the modem stack ranged from device drivers, over the porting of protocol-stack implementations, up to the network-configuration level. It goes without saying that this is an important building block for our ambition to run Genode on the Pinephone by the end of the year. Besides these prominent topics, the new version comes with many further improvements as summarized below. - Pluggable network device drivers - LTE modem stack - VirtualBox 6.1.14 - Improved USB pass-through for VirtualBox 5 - VirtIO block devices for virtual machines on ARM - Power-gating of PCI devices on x86 - Pine-A64-LTS single board computer - RISC-V update to privileged ISA 1.10 - VFS support for named pipes - OpenSSL 1.1.1i, curl 7.70.0 The full story is presented by our detailed release documentation at: https://genode.org/documentation/release-notes/21.02 Cheers Norman -- Dr.-Ing. Norman Feske Genode Labs https://www.genode-labs.com · https://genode.org Genode Labs GmbH · Amtsgericht Dresden · HRB 28424 · Sitz Dresden Geschäftsführer: Dr.-Ing. Norman Feske, Christian Helmuth

1 0

problem with permanent modification on Sculpt
by Edoardo Mantovani 23 Feb '21

23 Feb '21

Hello Everyone, Some hours ago I've installed Sculpt OS on my HDD through DD tool using ubuntu flashed from bootable USB. Now, the system flashes without any errors and everything seems cool, but there is only one problem: I am not able to apport any permanent modification to the OS, everything seems to live in RAM, I have also followed the section "Making customizations permanent" here[1], but also without clicking into the ram fs filesystem bottoms the /config/ folder resets itself after the reboot. Any Hints? Obviously, I would like to have a desktop OS that isn't volatile. (Sorry for the possibly dumb question but I've never had such types of problems) NOTE: Sculpt perfectly supports the hardware of my computer. [1] https://genode.org/documentation/articles/sculpt-20-02 Regards. Edoardo Mantovani, 2021 --- Edoardo Mantovani Independent security researcher email: Baseband(a)cpan.org Urbino, Italy

5 13

i2c driver on imx8q_evk board
by Jean-Adrien Domage 22 Feb '21

22 Feb '21

Dear Genodians, I am currently working on an i2c driver for the imx8q_evk board. I'm struggling to generate any kind of signal(s) on the i2c bus. First I had a look at os/src/drivers/touch/synaptic_dsx. I tried to run the i2c implementation from this driver on the i2c bus 2. It hang at the first _busy() call in the _start() method, i2c.h l:83. Please note that I skip all gpio and Event related part to make it work. Settings I used for I2c bus 2 -> irq: 68 ([1]) mmio:0x303a0000 ([2]), freq_div: 0x2a (64 for 400kHz) 1. Is this possible that this implementation is specific to the synaptic device? Then not working for others bus? 2. Reading [3], I noticed that _start() does not exactly follow this flowchart, is there any reason? Doing [4] is sufficient? 3. Do you have any other example of driver(s) using i2c like the touch/synaptic_dsx that may help me ? [1] IMX8MDQLQRM.pdf, chapter 7.1.2 A53 Interrupts, table 7-1 page 1023 [2] IMX8MDQLQRM.pdf, chapter 2.1.5 AIPS Memory Maps, table 2-5 page 28 [3] IMX8MDQLQRM.pdf, chapter 16.1 I2C Controller, Figure 16-7, page 6277 [4] IMX8MDQLQRM.pdf, chapter 16.1.5.1 Initialization sequence, page 6270 Thanks for your time. Cheers, Jean-Adrien Domage Software Engineer gapfruit AG

2 1

Help with nested signal context warnings
by Colin Parker 17 Feb '21

17 Feb '21

Hello Genodians, I'm hoping someone can help or point me to a good reference for the error that pops up occasionally saying "attempt to handle the same signal context twice (nested)". This happens within some Sculpt components (decorator, depot_query), but also happens in this USB wifi driver I'm trying to make. Mostly I want to understand it - my long explanation is below. My basic understanding is Genode gets upset when waiting for a signal within another signal handler. However, the "natural" way I would like this driver to behave is to be signal driven - all code is responding to some signal or other. However, sometimes one needs to do synchronous IO operations. If it is truly forbidden ever to wait within a signal handler, I considered a few options, but found all to be non-ideal. 1) Use stub signal handlers to insert elements into a work queue and drive everything from an event loop. This seems like reinventing the signal mechanism, but might be what's required. 2) Build state machines to break up synchronous IO operations with no waiting at all. This makes simple-looking operations complicated and increases debugging complexity. 3) Busy-wait for synchronous operations. Probably a big performance penalty, and obviously wasteful. So I proceeded, because I do notice that sometimes it is OK to wait within a handler (i.e. the warning does not occur). But I still get the warning other times, and I can't quite figure out when or why it happens. Initially, I thought that if I separated things out, so that, say, Signal_context A waits, but can only receive signals for Signal_context B or C, it would be OK. Now, I am not totally sure I've actually achieved this, but I think that I have, and I've become suspicious that I don't really understand the "rules." So, is there a way to understand when one can wait safely wait within a signal handler? Is it really as simple as "Signal A cannot be generated while waiting if a handler for A is on the stack?" Does the App vs IO signal distinction come into play (I have both). Also, is there a way to get a Genode app to output a stack trace - I can patch that warning mesage to output a stack trace and at least see what actually happened? Thanks as always to the Genode community for sharing your knowledge with me. Best regards, Colin

3 5

golang runtime
by Sergey Platonov 15 Feb '21

15 Feb '21

Hello all We have invested some time analyzing golang and how much it will take to make it production-ready. The build system requires some effort, and it's not fully clear if it's a one-time effort. Different golang projects use other build systems (bazel and so on). Networking is crucial for us, and we invested most of our time making it work. Unfortunately, we failed to do so: it seems the goroutines scheduler makes some assumptions that we overlooked. So, at the end of the day, we have a network that sometimes works. I have proposed a patch [1] that will fix some issues and hopefully help someone later on. Unfortunately, we will not invest more resources in porting golang since it seems too resource-consuming for our small team. [1] https://github.com/tor-m6/genode/pull/1 Regards, Sergey -- gapfruit AG Baarerstrasse 135 6300 Zug +41 762 444 560 sergey.platonov(a)gapfruit.com

2 3

general improvements for Sculpt
by Edoardo Mantovani 09 Feb '21

09 Feb '21

Hello for everyone, Some days ago I've used your os (Sculpt v.20.08) from bootable usb and I remained genuinely impressed regarding its style and its security base idea, after having read some informations on it, I was able to develop some tips which I would like to share with the community: ======================= Language Compatibility ======================= *) there is no support for Italian keyboard, I was able to find only german, french and english .chargen files, for a next update would be great to add other charger files. *) I can give my full support for translating document pages in Italian, this could (apparently) be great for increasing the possible audience, but Honestly I doubt that an Italian community could be created (we are quite far in the security-technological field, No comment on that, please). ======================= BEGINNER FRIENDLY OS? ======================= *) I know that this operating system is not developed to be user friendly, but it could be great to put some helps for beginners, like a graphical instruction box when clicking on certain things in Leitzentrale, a graphical example could be the following: |------------| |-------| | depot | (when clicking on it appears an info box) --> | info | |_______| |-------| (sorry for the bad ASCII image) ======================= GRAPHICS ======================= *) Probably the best point for your os consists on its graph graphics, the idea of Leitzentrale is innovative if we confront it to Windows os or similar, a small hint could be to create the same style for the "file" part, so something which could be similar to graphviz2 output instead of "block representation". { direct link to my idea: https://graphviz-perl.github.io/ see the graph under the "Input file # 17 - t/gen.parse.stt.t" example, s/other_names/folder_names/g } *) small consideration: I find some graphical glitch in the "motif decoration" 's node in Leitzentrale (it flew up and down without any input) [Still studying this..] ======================== DOCUMENTATIONS ======================== *)Your site is pretty cool and interesting, documentation is great but I haven't seen anything on Sculpt, could be great to add like UNIX's manpages system. ========================= WIRELESS SUBSYSTEM ========================= *) I asked for the documentation on it before speaking (Thanks Alexander), it is extremely similar to Linux wireless subsystem, except for a modified libnl support for user space, could I have the source code for it? I would like to study the modification you've apported for libnl. I am pretty fascinated by those modified subsystems. *) It would be great to extend the range for other devices, I saw you implemented only the iwlwifi driver, would be great to implement also brcmf (both HardMac and SoftMac) and even Qualcomm's wireless card, I can give my full support for that. /* *) I have some ideas for controlling the iwlwifi blob, for now I would like to test it on my own, in general it would be great to ""customize"" the "blob loading". */ ======================== Custom Patching system ======================== *) I've seen the potential of the software based hardware management, my biggest hint should be to implement a security patching system with a similar interface to Depot (something like: choose customization part, insert code patch [like linux's kernel system] and process it) | V could be a dangerous door for local-cyber-attacks ======================== TERMINAL DOWNSIDE ======================== *) Using the inspect shell I wasn't able to scroll up, do you know if it's implemented? It should be better to have a scroll bar, ======================= DEPOT SYSTEM ======================= As I understood, depot is like a package manager and the various repositories contains various applications, Here I'll insert my ideas on it: *) Many of those repos are inaccessible even if I am connected to the wireless network: { I am not able to download/fetch the following repos: [-] ehmry [-] blarson [-] rite } *) in general there isn't much variety in the repos, many packages are the same, it would be great to extend the "candidates" list, I can contribute to the development of several CLI apps. *) I can work for inserting some scripting languages interpreter packages inside Genode { [-] Minised [-] lightweight Perl languages (microperl, miniperl or my customized languages) } and maybe adapt them for the OS needs and tasks. *) A quite interesting idea would be to add local depots, In general: -->) We have 2 devices, (featured phones or similar) -->) The first is the client, the second is the depot server -->) through Bluetooth, BLE or even other standards (nfc??) could be cool to use the repository stored in the second phone into the first. [ Obviously this is extremely complex to do: we should set a correct cryptographic key exchange and set an authentication rule, this could lead an ∞ of problems: *) Hijacking or other Bluetooth attacks are possible, the worst case scenario is that an untrusted depot server can inject the device, bypassing the security authentication restriction. If this will be implemented, it MUST be well structured. *) Not every device has the same bluetooth version, with some works it could be implemented a workaround which act like a switch statement: { example: switch(bluetooth_version){ case (version == 5.0 ) {do this} case (version == 4.1 ) {do that} } } *) Obviously it must be implemented a tiny bluetooth subsystem, I suggest using Linux's one. (I have also the 2008-2009 documentation on it). *) This idea could be a great topic for your blog, I can help with the formal verifications (pi calculus?) exposition and with other implementation details. ] I have many other ideas, These are some "fast" considerations for improve the OS quality, my "knowledge CV" is here: (https://github.com/Baseband-processor) Let me know if you have some doubt, Regards and Thanks for you work, Edoardo Mantovani, 2021 -- Edoardo Mantovani Independent security researcher email: Baseband(a)cpan.org Urbino, Italy

5 9

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

users