f50d816555
If page faults are handled concurrently (as for base-nova) the traverse lookup call in rm_session_component must be thread safe, which it isn't. If the faulting area is backed by nested dataspaces which are managed by various rm_sessions then a race happens under following circumstances (triggered occasionally by the bomb test). The traverse lookup may return a pointer to a rm_session of a nested dataspace. If the rm_session is in parallel subject to destruction it happened that faults got enqueued to the faulters list of the deleted rm_session and internally to a list of the current rm_session of the Rm_client. During destruction of the faulting Rm_client the associated rm_session will be dissolved from the Rm_client, which leads to dereferencing the dangling pointer of the already destructed rm_session. On base-nova the memory of the rm_session object get unmapped eventually, so that the de-referencing of the dangling pointer caused page faults in core. The memory on other kernels inside core never get unmapped so that the bug doesn't trigger visible faults. The patch replace the keeping of a rm_session pointer by keeping a capability instead. The rm_session object must be looked up now explicitly in the Object_pool implementation, which implements proper reference counting on the rm_session object. Issue #549 |
||
|---|---|---|
| .. | ||
| etc | ||
| include | ||
| lib | ||
| mk | ||
| run | ||
| src | ||
| README | ||
This is generic part of the Genode implementation. It consists of two parts: :_Core_: is the ultimate root of the Genode application tree and provides abstractions for the lowest-level hardware resources such as RAM, ROM, CPU, and generic device access. All generic parts of Core can be found here - for system-specific implementations refer to the appropriate 'base-<system>' directory. :_Base libraries and protocols_: that are used by each Genode component to interact with other components. This is the glue that holds everything together.