- l4-hackers - example.com Site

Is there a service in L4 packages like shell in Linux?
by chenggh 29 Aug '06

29 Aug '06

Hi, I think if a servive in l4/pkgs like shell in Linux exists it will help the L4-user very much. We could start or stop a seriver like creating or destroying a process in Linux. I don't know whether there is a server like this? If it is not done I want to have a development with this server. thank you! chenggh

2 1

Amount of threads per task?
by Oskar Senft 28 Aug '06

28 Aug '06

Hi L4 Hackers! When creating new threads within the L4Linux kernel, I "sometimes" (whatever that means) get the following output and error: *l4lx | l4lx_thread_create: Created thread 0e.1a (Command) --Thread names exhausted!--------------------------------IP: 0050758e What does that mean? After pressing "g", the system continues running. However when I try to kill the thread later, I get the following: --Unknown TID to delete thread name!---------------------IP: 0050760a Is it not possible to create more than 0x19 = 25 threads within the L4Linux kernel? Or am I doing anything wrong? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

3 5

L4Linux threads - interrupt context
by Oskar Senft 28 Aug '06

28 Aug '06

Hi L4Linux hackers! When creating threads within the L4Linux kernel and running the command l4x_prepare_irq_thread(current_thread_info()); the thread obviously ;-) is being run in the interrupt context. This means the thread (let's call it thread X) must not sleep and is restricted in other ways. This implies, that I cannot run Linux functions that would cause the thread X to sleep - that's clear. On top of that, let's create the following scenario: some other task issues an IPC call to the described L4Linux thread X waiting for IPC. For handling the call, thread X would need to use Linux functions causing thread X to sleep. This will cause a kernel panic, deadlock or other severe errors. Our idea for solving that is to use *another* "normal" *Linux* thread (let's call it Z) not running in interrupt context. This thread Z would sleep until it is awakened by the L4Linux thread X and then call the Linux function that causes thread Z to sleep. But: the L4Linux thread X would have to send a reply to the IPC call immediately. So, I would need another L4 thread Y (not known to L4Linux), acting as a notifier thread for the calling task. This thread would receive the IPC notify call, go into a L4 semaphore waiting to be woken by thread Z. So, the simple IPC call from another task which should use a Linux function requires *three* threads to run ... If we had the possiblity to send the reply to an incoming IPC from _another_ thread than the called thread, this at least would eliminate the notifier thread Y. If we had the possibility to run L4Linux threads (like thread X) in some Linux context where it could sleep, this could even eliminate both threads Y and Z. Is there a simpler solution? Is it possible to make it easier? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

NICTA-Ericsson secure-OS collaboration
by Gernot Heiser 26 Aug '06

26 Aug '06

For those who haven't looked at l4hq.org recently: NICTA and Ericsson have announced a research collaboration, among others on secure embedded operating systems. This is based on NICTA's L4-embedded/Iguana operating system. Gernot

1 0

L4.sec implementation and formal verification
by William DUCK 26 Aug '06

26 Aug '06

Hello Misters, As you are microkernel experts, I am asking your help. I am attempting to build up a team. I believe it's time for a full-fledge verified OS. If somebody is interested in functional programming and in formal methods to help to implement the L4.sec kernel , he is welcome :) Here is an example of a protocol formalisation : network stack : http://www.cl.cam.ac.uk/~pes20/Netsem/ If you want to contact me, my mail is guillaume_dot_fortaine_at_wanadoo_dot_fr I will set up a mailing-list, a web server, a wiki and an IRC Best Regards, Guillaume FORTAINE

2 1

Re: L4Linux threads - interrupt context
by Bjoern Doebel 25 Aug '06

25 Aug '06

2 3

TPM Emulator with L4Linux
by Andreas Niederl 24 Aug '06

24 Aug '06

Hi, has anybody successfully used the TPM Emulator[1] module with L4Linux? I have been trying using it with TrouSerS[2] but fail on starting tcsd with the following two errors (always one of them but never both at the same time): gentoo-l4 TDDL[4480]: tddl.c:105 Calling write to driver gentoo-l4 tpm_emulator tpm_emulator-0.4/./linux_module.c:113: Debug: tpm_ioctl(21505, 0808e500) gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4156: Debug: tpm_handle_command() gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:3473: Info: The tag value sent to for a command (0x6564) is invalid gentoo-l4 TCS[4480]: tcs_utils.c:260 ERROR: TCS GetCapability failed with result = 0x1e and gentoo-l4 TDDL[4483]: tddl.c:105 Calling write to driver gentoo-l4 tpm_emulator tpm_emulator-0.4/./linux_module.c:113: Debug: tpm_ioctl(21505, 0808e500) gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4156: Debug: tpm_handle_command() gentoo-l4 tpm_emulator tpm_emulator-0.4/tpm/tpm_cmd_handler.c:4160: Error: tpm_unmarshal_TPM_REQUEST() failed gentoo-l4 TDDL[4483]: tddl.c:148 ERROR: Zero bytes read from device /dev/tpm gentoo-l4 TCS[4483]: tcs_utils.c:260 ERROR: TCS GetCapability failed with result = 0x1087 I guess that something is going wrong with the call to ioctl from tddl but wasn't able to figure it out yet. Are there modifications necessary for using modules with L4Linux? Regards, Andi [1] http://tpm-emulator.berlios.de/ [2] http://trousers.sourceforge.net/

2 2

L4Linux with serial console / IRQ usage
by Andreas Niederl 24 Aug '06

24 Aug '06

Hi, I have been trying to get a serial console on L4Linux with the stub drivers and encountered the message 'l4ser: vkey_irq not set - input disabled!'. Unfortunately I don't know which IRQ number is required here. I tried passing some different values to L4Linux which resulted in the error message 'irq_thread: RMGR denied IRQ 4: Code 0x1'. I'd be grateful for some hints on that. I also noticed that there are several different ways for handling IRQs (omega0, rmgr, l4io, ...) which require different options for some servers and L4Linux. Are there any documents describing the IRQ handling in L4Env and how to follow one of these ways consistently? /boot/grub/menu.lst: title L4Linux-2.6 kernel /boot/bootstrap -serial modaddr 0x02000000 module /boot/bin/fiasco -nowait -nokdb -serial -serial_esc -comport 1 module /boot/bin/sigma0 module /boot/bin/roottask task modname "bmodfs" attached 5 modules module /boot/bin/names module /boot/bin/log module /boot/bin/dm_phys module /boot/bin/simple_ts -t 300 module /boot/bin/rtc module /boot/bin/l4io --noirq module /boot/bin/tftp -i module /boot/bin/bmodfs module /boot/bin/libld-l4.s.so module /boot/bin/libloader.s.so module /boot/bin/run-script module /boot/bin/vmlinuz26 module /boot/bin/drops-rd.rd module /boot/bin/loader --fprov=BMODFS run-script /boot/bin/run-script: modpath "/boot/bin" sleep 2 task "vmlinuz26" "mem=64M load_ramdisk=1 ramdisk_size=17000 root=/dev/ram l4env_rd=/boot/bin/drops-rd.rd console=ttyLv0 l4ser.vkey_irq=4" priority 0xA0 all_sects_writable Regards, Andi

3 15

No keyboard with L4Linux
by FERANDELLE Pascal 23 Aug '06

23 Aug '06

I boot L4Linux-2.6 on Fiasco, using l4con on a graphical console, and the drops ramdisk. Everything boots well, and I obtain the "dropsbox login:", but, unfortunately, I have no keyboard entry ... In the previous kernel messages, there is one saying : i8042.c: Can't read CTR while initializing i8042 Can it be related to my problem ? Thanks Pascal

2 1

Re: Booting L4Linux/Fiasco with root=/dev/hda
by Bjoern Doebel 23 Aug '06

23 Aug '06

1 0

Booting L4Linux/Fiasco with root=/dev/hda
by FERANDELLE Pascal 23 Aug '06

23 Aug '06

I try to boot L4Linux (kernel 2.6.17) on Fiasco, on a PC which has already RedHat Enterprise Linux 4.0 installed, with root=/dev/hda3. The Linux kernel begins to boot, but after the messages : ... kjournald starting. Commit interval 5 seconds EXT3 FS on hda3, internal journal EXT3-fs: mounted filesystem with ordered data mode VFS: Mounted root (ext3 filesystem) Warning: unable to open an initial console Nothing else appears on the screen, but I can see the station is still alive, because the disk led is still highlightening frequently, then everything stops, and I have the message "Restarting system" on the screen. Nothing else happens ... Any idea, first for the opening problem of the console, and then, about what can happen after that, would be nice !!! Thanks Pascal PS : here is my grub.conf file and my linux26.cfg file --- grub.conf --- title L4_Linux 2.6 root (hd0,0) kernel /l4_linux/bootstrap vbeset 0x117 modaddr 0x06000000 module /l4_linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module /l4_linux/sigma0 module /l4_linux/roottask task modname "bmodfs" attached 4 modules module /l4_linux/events module /l4_linux/names -events module /l4_linux/log module /l4_linux/dm_phys --isa=0x00800000 -v --events module /l4_linux/simple_ts -t 300 --events module /l4_linux/rtc --events module /l4_linux/l4io -noirq --events # module /l4_linux/l4exec --events module /l4_linux/con -l4io --events # module /l4_linux/l4dope -l4io --events module /l4_linux/bmodfs --events module /l4_linux/libld-l4.s.so module /l4_linux/libloader.s.so module /l4_linux/linux26.cfg module /l4_linux/vmlinuz26 module /l4_linux/loader --fprov=BMODFS linux26.cfg --- linux26.cfg --- modpath "(hd0,0)/l4_linux" task "vmlinuz26" "earlyprintk=yes mem=64M video=l4fb root=/dev/hda3" all_sects_writable

1 0

Where is the definition of hi_server_loop() function?
by chenggh 23 Aug '06

23 Aug '06

Hi, Everyone: Now I am reading the document of Building Infrastructures for DROPS Tutorial. And in the server side the code is like this: #include <stdio.h> #include <l4/names/libnames.h> #include "hiworld-server.h" char LOG_tag[9]="hiserver"; static int count; void hi_print_component(CORBA_Object _dice_corba_obj, CORBA_Environment *_dice_corba_env){ printf("Hi world\n"); count++; } int hi_count_component(CORBA_Object _dice_corba_obj, CORBA_Environment *_dice_corba_env){ return count; } int main(void){ if(names_register("hiworld")==0){ printf("Error registering at nameserver\n"); return 1; } hi_server_loop(0); } In the main routine there is function named hi_server_loop. But I don't where is the function definition. i checked the hiworld-server.h and there is no definition. ths chenggh

2 1

Problem of l4lx_thread kmalloc
by 강후영 22 Aug '06

22 Aug '06

Hi, I created l4lx_threads by "l4lx_thread_create()". But when these threads alloccate some memory by kmalloc(), fault error always occurs as fallow, l4lx | L4RM: [PF] read at 0x999999b0, eip 0042e30a, src E.0B l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault What is the problem? Is there some size limitation of kmalloc for thease threads? I tried to allocate a few KBs. Best regards

2 1

L4 bug report
by chenggh 21 Aug '06

21 Aug '06

hi, everyone: Today I use ubuntu 6.06 to compile the l4. There are some error messages like this: make[2]: Entering directory `/home/fiasco/L4/l4/tool/gcc-wrap' ... Building .general.d make[2]: Leaving directory `/home/fiasco/L4/l4/tool/gcc-wrap' make[2]: Entering directory `/home/fiasco/L4/l4/tool/gcc-wrap' ... Generating drops-ar.Linux sed '\ s,@system@,Linux,g;\ s,@ar@,ar,g;\ s,@nm@,nm,g;\ s,@ranlib@,ranlib,g;\ s,@cc@,gcc,g;\ s,@cxx@,g++,g;\ s,@l4dir@,,g;\ s,@dropsdir@,/home/fiasco/L4/,g;\ s,@compilerincdir@,/usr/lib/gcc/i486-linux-gnu/3.4.6/include,g;\ s,@libgcc@,/usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc.a,g;\ s,@libgcc_eh@,/usr/lib/gcc/i486-linux-gnu/3.4.6/libgcc_eh.a,g;\ s,@default_system@,x86_586-l4v2,g;\ s,@default_arch@,x86,g;\ s,@default_cpu@,586,g;\ s,@default_l4api@,l4v2,g; \ ' drops-ar.in > drops-ar.Linux.new sed: -e expression #1, char 452: unterminated address regex make[2]: *** [drops-ar.Linux] Error 1 make[2]: Leaving directory `/home/fiasco/L4/l4/tool/gcc-wrap' make[1]: *** [gcc-wrap] Error 2 make[1]: Leaving directory `/home/fiasco/L4/l4/tool' make: *** [tool] Error 2 I doubted that it is sed version's problem. In ubuntu 6.06 the sed is NU sed version 4.1.4. chenggh

2 2

l4linux-2.6 does not build
by Stefan Scheler 19 Aug '06

19 Aug '06

Hello, current cvs version of l4linux does not build (please see attached log). Resolving this by putting the headers manually in the right place gives more errors like that. There must be something broken in the build process. Thanks for help. Stefan Creating asm-l4/api-l4env -> asm/api symlink Creating asm-l4/l4lxapi/impl symlink Creating asm-l4/l4x-i386 -> asm/l4x symlink Creating asm-l4/l4-arch/asm symlink Creating asm-l4/i386-arch/asm symlink CHK include/linux/version.h UPD include/linux/version.h SYMLINK include/asm -> include/asm-l4 SPLIT include/linux/autoconf.h -> include/config/* CC arch/l4/kernel/asm-offsets.s In file included from include/asm-l4/l4-arch/asm/processor.h:12, from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/segment.h:8:28: l4/sys/segment.h: No such file or directory In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/processor.h:25:26: l4/sys/types.h: No such file or directory In file included from include/asm-l4/i386-arch/asm/thread_info.h:17, from include/linux/thread_info.h:21, from include/linux/preempt.h:10, from include/linux/spinlock.h:50, from include/linux/capability.h:45, from include/linux/sched.h:7, from arch/l4/kernel/asm-offsets.c:8: include/asm-l4/l4-arch/asm/processor.h:407: error: syntax error before "l4_threadid_t" include/asm-l4/l4-arch/asm/processor.h:407: warning: no semicolon at end of struct or union include/asm-l4/l4-arch/asm/processor.h:408: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:409: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:410: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:411: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:412: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:413: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:414: error: syntax error before ':' token include/asm-l4/l4-arch/asm/processor.h:426: error: syntax error before '}' token In file included from arch/l4/kernel/asm-offsets.c:8: include/linux/sched.h:804: error: field `thread' has incomplete type In file included from include/asm-l4/l4-arch/asm/suspend.h:6, from include/linux/suspend.h:5, from arch/l4/kernel/asm-offsets.c:11: include/asm-l4/l4-arch/asm/desc.h: In function `write_ldt_entry': include/asm-l4/l4-arch/asm/desc.h:116: warning: implicit declaration of function `fiasco_ldt_set' include/asm-l4/l4-arch/asm/desc.h: In function `load_TLS': include/asm-l4/l4-arch/asm/desc.h:130: warning: implicit declaration of function `fiasco_gdt_set' include/asm-l4/l4-arch/asm/desc.h:130: error: dereferencing pointer to incomplete type include/asm-l4/l4-arch/asm/desc.h:130: error: dereferencing pointer to incomplete type make[1]: *** [arch/l4/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2

3 3

build problems with dice
by chenggh 17 Aug '06

17 Aug '06

hi: when I try to compile the dice, there are some errors like this: /home/chenggh/L4/l4/tool/dice/src/CDCEParser.cpp:264: undefined reference to `dce_flex_debug' CCORBAParser.o: In function `CCORBAParser::Import(std::basic_string<char, std::char_traits<char>, std::allocator<char> >)': /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:93: undefined reference to `GetCurrentBufferCorba()' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:154: undefined reference to `RestoreBufferCorba(void*, bool)' CCORBAParser.o: In function `CCORBAParser::Parse(void*, std::basic_string<char, std::char_traits<char>, std::allocator<char> >, int, bool, bool)': /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:231: undefined reference to `corba_flex_debug' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:245: undefined reference to `RestoreBufferCorba(void*, bool)' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:257: undefined reference to `GetCurrentBufferCorba()' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:241: undefined reference to `corbain' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:242: undefined reference to `StartBufferCorba(_IO_FILE*)' /home/chenggh/L4/l4/tool/dice/src/CCORBAParser.cpp:236: undefined reference to `corba_flex_debug' CPreProcess.o: In function `CPreProcess::PreProcess(std::basic_string<char, std::char_traits<char>, std::allocator<char> >, bool, bool)': /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:343: undefined reference to `incin' /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:344: undefined reference to `incout' /home/chenggh/L4/l4/tool/dice/src/CPreProcess.cpp:348: undefined reference to `inclex()' ./src/parser/dce/libdce.a(parser.o): In function `dceparse()': /home/chenggh/L4/l4/tool/dice/src/parser/dce/parser.yy:3577: undefined reference to `dcelex(yystype*)' ./src/parser/dce/libdce.a(parser.o): In function `dceparse()': /usr/share/bison/bison.simple:574: undefined reference to `dcelex(yystype*)' ./src/parser/corba/libcorba.a(parser.o): In function `corbaparse()': /usr/share/bison/bison.simple:574: undefined reference to `corbalex(yystype*)' ./src/parser/gcc-c/libg I checked the old mailist again. Somebody else encountered the same problem with me. I use g++3.3.6 and bison 1.35. My host OS is ubuntu 5.10. How to fix it? thank you chenggh

2 1

L4Linux-2.6.17 on Fiasco
by FERANDELLE Pascal 12 Aug '06

12 Aug '06

Hi, I try to run L4Linux-2.6.17 on Fiasco, on native PC, and I have problems. As I got the following error : ... l4lx | Filling lower ptabs l4lx | Done (1643 entries) l4lx | l4lx_thread_create: Created thread 0e.05 (timer.i0) DMphys | ds 36, client E.00, rights 0x0003, has 0x0001 DMphys | [8.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): DMphys | DMphys: bad permissions l4lx | L4RM: dataspace at 0x00400000-0x00614fff, id 36 at 8.00 l4lx | L4RM: dataspace manager call failed ("permission denied") l4lx | L4RM: [PF] write at 0x004025ec, ip 0040b53c, src E.02 l4lx | [E.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): l4lx | unhandled page fault after looking at the mailing list, it seems the "Use ldso for loading" option has to be configured for L4Linux. I did so, but now, the load stops with the following messages : loader | vmlinuz26 : Starting application using libld-l4.s.so loader | vmlinuz26,#e : Loading binary loader | vmlinuz26,#e : Loading ldso loader | vmlinuz26,#e : Starting libld-l4.s.so at 00013870 via 0000bf60 then messages from io about PCI configuration, and go to jdb with message : (e.00) jdb: --__main() returned My grub.conf file is as following : title L4_Linux 2.6 root (hd0,0) kernel /l4_linux/bootstrap modaddr 0x06000000 module /l4_linux/main -nowait -nokdb -serial_esc -comspeed 115200 -comport 1 module /l4_linux/sigma0 module /l4_linux/roottask task modname "bmodfs" attached 4 modules module /l4_linux/events module /l4_linux/names -events module /l4_linux/log module /l4_linux/dm_phys --isa=0x00800000 -v --events module /l4_linux/simple_ts -t 300 --events module /l4_linux/l4io -noirq --events module /l4_linux/l4exec --events # module /l4_linux/con -l4io -cpuload --events module /l4_linux/bmodfs --events module /l4_linux/libld-l4.s.so module /l4_linux/libloader.s.so module /l4_linux/linux26.cfg module /l4_linux/vmlinuz26 module /l4_linux/loader --fprov=BMODFS linux26.cfg and my linux26.cfg file : modpath "(hd0,0)/l4_linux" task "vmlinuz26" "earlyprintk=yes mem=64M root=/dev/hda3" all_sects_writable Any help would be great !!! Thanks Pascal

2 1

Re: current_thread_info
by Oskar Senft 12 Aug '06

12 Aug '06

Hi! >>> You need to call l4x_prepare_irq_thread(current_thread_info()) in your >>> thread before doing anything serious in there. >> Ok, sounds good. Unfortunately I cannot find it in my snapshot (May >> 5th, 2006) - since when should it have been in? > > l4x_setup_ti_thread_stack_irq(current_thread_info()) Great, thank you! That solved my problem. Could you please add the necessary line EXPORT_SYMBOL(l4x_setup_ti_thread_stack_irq); in arch/l4/kernel/main.c ? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

The "region overlap" problem in the L4/Fiasco hello example
by chenggh 12 Aug '06

12 Aug '06

Hi,everyone: When I boot the hello example in the L4/Fiasco. there is a "region overlap" in the booting information. I don't why it could be like this. The grub configuration and the error information is following: Grub: title fiasco_hello_new kernel (hd0,1)/boot/fiasco_hello_new/bootstrap -comport 1 -serial module (hd0,1)/boot/fiasco_hello_new/main -nokdb module (hd0,1)/boot/fiasco_hello_new/sigma0 module (hd0,1)/boot/fiasco_hello_new/roottask module (hd0,1)/boot/fiasco_hello_new/hello minicom_log: L4 Bootstrapper Loading (hd0,1)/boot/fiasco_hello_new/main Kernel at 00002000-0038f408 Detected new-style DD-L4(v2)/Fiasco x86 Loading (hd0,1)/boot/fiasco_hello_new/sigma0 Loading (hd0,1)/boot/fiasco_hello_new/roottask loaded module section: [0028d000-00324e13) .Roottask syms/lines (copy) overlaps with: [00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main [00002000-0005ae70) (hd0,1)/boot/fiasco_hello_new/main [0005b000-0005fcfd) (hd0,1)/boot/fiasco_hello_new/main [00090000-0009432d) (hd0,1)/boot/fiasco_hello_new/sigma0 [00095340-00096824) (hd0,1)/boot/fiasco_hello_new/sigma0 [0009f000-00100000) BIOS area [00100000-0010dc04) bootstrap [0013f000-0028ccb0) Modules Memory [00300000-0038f408) (hd0,1)/boot/fiasco_hello_new/main [1dff0000-ffffffff) Deep Space region overlap Thanks! Cheng

4 3

current_thread_info
by Oskar Senft 11 Aug '06

11 Aug '06

Hi L4Linux experts! Is it right, that the function current_thread_info (and dependent functions like "current") should not be called from threads which are created by "l4lx_thread_create"? I always get pagefaults while trying this ... *l4lx | L4RM: [PF] read at 0x99999c50, ip 004f9afe, src E.16 Is there a possibility to enable this function? Regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 519 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 1

Re: L4Linux + Fiasco-ux
by Daniel Vandersee 10 Aug '06

10 Aug '06

Adam Lackorzynski wrote: > On Wed Aug 09, 2006 at 17:47:16 +0200, Daniel Vandersee wrote: > >>Adam Lackorzynski wrote: >> >>>Please enable "Use ldso for loading" in the L4Linux configuration. >>>Should also be default by tomorrow. >>> >> >>Thank you, but now the loader complains about a missing libld-l4.s.so >>which I can't find anywhere. > > > libld-l4.s.so is built in the ldso package. > I dowloaded the ldso package and recompiled l4linux (with ldso) as well as l4env, but I'm afraid this was wasn't the problem - I still get the same error. > loader | vmlinuz26.ux: Starting application using libld-l4.s.so > loader | vmlinuz26.ux,#f: Loading binary > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/libld-l4 > fuxfprov: .s.so" by D.02 > loader | vmlinuz26.ux,#f: Loading ldso > loader | vmlinuz26.ux,#f: Starting libld-l4.s.so at 00013e40 via 0000bba8 > fuxfprov| open "./libloader.s.so" by F.00 > fuxfprov| Can't open "./libloader.s.so": -2 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/./libloa > fuxfprov: der.s.so" by F.00 > fuxfprov| open "vmlinuz26.ux" by F.00 > fuxfprov| Can't open "vmlinuz26.ux": -2 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/vmlinuz2 > fuxfprov: 6.ux" by F.00 > l4lx | ======> L4Linux 2.6 starting... <======== > l4lx | Linux version 2.6.17-l4 (user@kubuntu) (gcc-Version 3.3.6 (Ubuntu 1: > l4lx : 3.3.6-8ubuntu1)) #4 Wed Aug 9 18:41:29 CEST 2006 > l4lx | Binary name: vmlinuz26.ux > l4lx | Kernel command line (9 args): mem=64M load_ramdisk=1 ramdisk_size=163 > l4lx : 84 root=1:0 l4env_rd=/home/user/ext/l4env_060809/DROPS/bin/x86_58 > l4lx : 6/l4v2/rd1 panicblink=0 lang=de video=l4fb:640x400@16,xpos:10,ypos:10 > l4lx : ,refreshsleep:150,title:DamnSmallLinux noirq > l4lx | Image: 00400000 - 0068f000 [2620 KiB]. > l4lx | Areas: Text: 00400000 - 005c6000 [1816kB] (a bit longer) > l4lx | Data: 005c6000 - 006025ac [241kB] > l4lx | Initdata: 00606000 - 00626000 [128kB] > l4lx | BSS: 00626000 - 0068d1c0 [412kB] > l4lx | l4lx_thread_create: Created thread 0f.03 (tamer) > l4lx | Using tamed mode. > l4lx | l4lx_thread_create: Created thread 0f.04 (server) > l4lx | main thread will be 0f.04 > l4lx | l4env_register_pointer_section: addr = 00604000 size = 569344 > l4lx | sec-w-init: virt: 0x00604000 to 0x0068efff [556 KiB] > l4lx | Noncontiguous region for sec-w-init > l4lx | sec-w-init: Number of physical regions: 2, 569344 Bytes > l4lx | sec-w-init: 1: Phys: 0x0141c000 to 0x0148d000, Size: 462848 > l4lx | sec-w-init: 2: Phys: 0x00ae6000 to 0x00b00000, Size: 106496 > l4lx | l4env_linux_startup thread 4. > l4lx | main thread: received startup message. > l4lx | Main thread running, waiting... > l4lx | setup_l4env_memory: Forcing superpages for main memory > l4lx | Main memory size: 64MB > l4lx | Main memory: virt: 0x00800000 to 0x047fffff [65536 KiB] > l4lx | Main memory: Number of physical regions: 1, 67108864 Bytes > l4lx | Main memory: 1: Phys: 0x0a400000 to 0x0e400000, Size: 67108864 > l4lx | Filling lower ptabs... > l4lx | Done (1260 entries). > l4lx | l4env_rd_path: /home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2 > l4lx : /rd1 > l4lx | Loading: /home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1 > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1" by > fuxfprov: F.04 > l4lx | INITRD: Size of RAMdisk is 16384KiB > l4lx | RAMdisk from 04800000 to 05800000 [16384KiB] > l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) > DMphys | ds 81, client F.00, rights 0x0003, has 0x0001 > DMphys | [7.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): > DMphys | DMphys: bad permissions > l4lx | L4RM: dataspace at 0x00400000-0x005c5fff, id 81 at 7.00 > l4lx | L4RM: dataspace manager call failed ("permission denied") > l4lx | L4RM: [PF] write at 0x00402860, ip 0040b2bc, src F.02 > l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault > > --PANIC, 'g' for exit-------------------------------ESP:00629d20 EIP:a00bdcd3 > (f.00) jdb: ^ Kind regards, Daniel

3 3

L4Linux output on serial line?
by Andreas Niederl 09 Aug '06

09 Aug '06

Hi, I would like to have the output from the L4Linux kernel on the serial line for debugging purposes because Qemu doesn't allow me to scroll back in its output window. Could somebody give me hints on how to doing that? I already configured Grub for having serial support from bootstrap and Fiasco. Regards, Andi

1 1

exec doesn't respect all_sects_writable
by Andreas Niederl 09 Aug '06

09 Aug '06

Hi, I wanted to run a current L4Linux using the CVS version of DROPS and got a page fault when the Linux code is self-modified. I was told to use the option all_sects_writable for the loader, but this apparently does not work when not using ldso. Exec seems to ignore this option and maps in the L4Linux space read only. This looks like a bug to me. Regards, Andi

2 2

L4Linux + Fiasco-ux
by Daniel Vandersee 09 Aug '06

09 Aug '06

Hello, when I try to run L4Linux (compiled for ux) on top of Fiasco-ux I get the following error: $./lx con ... > fuxfprov| open "/home/user/ext/l4env_060809/DROPS/bin/x86_586/l4v2/rd1" by > fuxfprov: F.04 > l4lx | INITRD: Size of RAMdisk is 16384KiB > l4lx | RAMdisk from 04800000 to 05800000 [16384KiB] > l4lx | l4lx_thread_create: Created thread 0f.05 (timer.i0) > DMphys | ds 67, client F.00, rights 0x0003, has 0x0001 > DMphys | [7.0] dm_phys/server/src/map.c:620:if_l4dm_generic_fault_component(): > DMphys | DMphys: bad permissions > l4lx | L4RM: dataspace at 0x00400000-0x005c5fff, id 67 at 7.00 > l4lx | L4RM: dataspace manager call failed ("permission denied") > l4lx | L4RM: [PF] write at 0x004026d0, ip 0040b2bc, src F.02 > l4lx | [F.0] l4rm/lib/src/pagefault.c:78:__unknown_pf(): > l4lx | unhandled page fault > > --PANIC, 'g' for exit-------------------------------ESP:0000893c EIP:000223b3 > (f.00) jdb: I tried several L4Linux configurations without success. Any help would be appreciated. Kind regards, Daniel

2 1

L4 Semaphore in L4Linux
by Oskar Senft 09 Aug '06

09 Aug '06

Hi! Is it possible to use the L4 Semaphore and Lock within a L4Linux kernel module somehow? I believe, that both is already used within the L4Linux kernel itself, but the symbols are not exported to other kernel module. When I now try to use them, the linker tells that the following symbols are undefined: "l4semaphore_restart_down" "l4semaphore_restart_up" "l4thread_myself" "l4semaphore_thread_l4_id" If I try to add the libsemaphore.a, the situation gets worse and the following symbols are undefined. "LOG_flush" "_exit" "l4thread_create_long" l4thread_get_prio" "l4sigma0_kip_kernel_has_feature" "l4thread_l4_id" "l4thread_myself" "l4thread_data_set" "l4thread_data_get" "LOG_logL" "l4thread_set_prio" "l4thread_data_allocate_key" Even adding more libs to the L4Linux kernel module does not resolve all symbols - I'm not even sure if that could work at all. These are the libs already linked in (and making the kernel module work - without semaphores / locks): libdm_generic.a \ libl4env.a \ libl4env_err.a \ libgeneric_blk-server.a \ libl4sys.a \ libnames.a \ libroot.o.a \ libdiet_c.a \ I also tried to simply load the kernel module with unresolved symbols - in hope that the running kernel would solve it - to no success. Does anyone have a solution to this? Best regards Oskar. -- Sirrix AG security technologies - http://www.sirrix.com Oskar Senft eMail: o.senft(a)sirrix.com Tel +49 (681) 936 251 - 119 Fax +49 (681) 936 251 - 500 get public key from keyserver Fingerprint 6FC6 3E44 233F 7F4B 33C7 A8D0 2EDA F3BA B5A3 0BA4 This message may contain confidential and/or privileged information. If you are not the addressee, you must not use, copy, disclose or take any action based on this message or any information herein. If you have received this message in error, please advise the sender immediately by reply e-mail and delete this message.

2 4