base-linux ram dataspace file descriptor usage
kliemann at ...543...
Fri Mar 23 18:19:22 CET 2018
I'm struggling with modifying the Ram_dataspace in base-linux.
I have replaced the file descriptor opened in
> void Ram_dataspace_factory::_export_ram_ds(Dataspace_component *ds)
in base-linux/src/core/ram_daraspace_support.cc by opening a special
device file that provides mappable ram.
I have attached the exact diff that causes the segfault. The kernel
module that provides the device file and the ioctl is available at .
I have tested it on a Linux system and mapping memory and
reading/writing it worked flawlessly.
With this change each component creates a segmentation fault. I was not
able to trace it, I couldn't even find out in which file it occurs.
The instruction pointer randomly appeared in
repos/base/src/lib/base/lock.cc or in repos/base/src/lib/base/heap.cc. I
have touched neither of these files.
Is there any information about where this is used exactly? I was unable
to trace the usage of the mapped memory beyond Region_map_mmap::attach.
I have also traced the calls inside the kernel module and it looks as it
only uses open, mmap and close so there shouldn't a problem.
I'd like to give you further information about this but I have
absolutely no idea by myself.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 1816 bytes
Desc: not available
More information about the users