ehmry/genode
ehmry/genode
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
bf92232698
genode/repos/ports/src/noux/local_rom_service.h

82 lines
2.1 KiB
C
Raw Normal View History

noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
/*
* \brief ROM service provided to Noux processes
* \author Norman Feske
* \date 2013-07-18
*
* The local ROM service has the sole purpose of tracking ROM dataspaces
* so that they are properly detached from RM sessions when the corresponding
* ROM sessions are closed.
*/
/*
Adjust file headers to refer to the AGPLv3
2017-02-20 13:23:52 +01:00
* Copyright (C) 2013-2017 Genode Labs GmbH
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
*
* This file is part of the Genode OS framework, which is distributed
Adjust file headers to refer to the AGPLv3
2017-02-20 13:23:52 +01:00
* under the terms of the GNU Affero General Public License version 3.
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
*/
#ifndef _NOUX__LOCAL_ROM_SERVICE_H_
#define _NOUX__LOCAL_ROM_SERVICE_H_
/* Genode includes */
#include <base/service.h>
/* Noux includes */
#include <dataspace_registry.h>
#include <rom_session_component.h>
namespace Noux {
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
typedef Local_service<Rom_session_component> Local_rom_service;
class Local_rom_factory;
}
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
class Noux::Local_rom_factory : public Local_rom_service::Factory
{
private:
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
VFS: nonblocking interface The VFS library can be used in single-threaded or multi-threaded environments and depending on that, signals are handled by the same thread which uses the VFS library or possibly by a different thread. If a VFS plugin needs to block to wait for a signal, there is currently no way which works reliably in both environments. For this reason, this commit makes the interface of the VFS library nonblocking, similar to the File_system session interface. The most important changes are: - Directories are created and opened with the 'opendir()' function and the directory entries are read with the recently introduced 'queue_read()' and 'complete_read()' functions. - Symbolic links are created and opened with the 'openlink()' function and the link target is read with the 'queue_read()' and 'complete_read()' functions and written with the 'write()' function. - The 'write()' function does not wait for signals anymore. This can have the effect that data written by a VFS library user has not been processed by a file system server yet when the library user asks for the size of the file or closes it (both done with RPC functions at the file system server). For this reason, a user of the VFS library should request synchronization before calling 'stat()' or 'close()'. To make sure that a file system server has processed all write request packets which a client submitted before the synchronization request, synchronization is now requested at the file system server with a synchronization packet instead of an RPC function. Because of this change, the synchronization interface of the VFS library is now split into 'queue_sync()' and 'complete_sync()' functions. Fixes #2399
2017-08-15 20:51:53 +02:00
Allocator &_alloc;
Env &_env;
Rpc_entrypoint &_ep;
VFS: construct file-systems using Vfs::Env object Reduce the size and forward compatibility of VFS file-system constructors by passing an object holding accessors for 'Genode::Env', 'Genode::Allocator', response handlers, and the root file-system. Fix #2742
2018-04-03 15:59:35 +02:00
Vfs::File_system &_root_dir;
VFS: nonblocking interface The VFS library can be used in single-threaded or multi-threaded environments and depending on that, signals are handled by the same thread which uses the VFS library or possibly by a different thread. If a VFS plugin needs to block to wait for a signal, there is currently no way which works reliably in both environments. For this reason, this commit makes the interface of the VFS library nonblocking, similar to the File_system session interface. The most important changes are: - Directories are created and opened with the 'opendir()' function and the directory entries are read with the recently introduced 'queue_read()' and 'complete_read()' functions. - Symbolic links are created and opened with the 'openlink()' function and the link target is read with the 'queue_read()' and 'complete_read()' functions and written with the 'write()' function. - The 'write()' function does not wait for signals anymore. This can have the effect that data written by a VFS library user has not been processed by a file system server yet when the library user asks for the size of the file or closes it (both done with RPC functions at the file system server). For this reason, a user of the VFS library should request synchronization before calling 'stat()' or 'close()'. To make sure that a file system server has processed all write request packets which a client submitted before the synchronization request, synchronization is now requested at the file system server with a synchronization packet instead of an RPC function. Because of this change, the synchronization interface of the VFS library is now split into 'queue_sync()' and 'complete_sync()' functions. Fixes #2399
2017-08-15 20:51:53 +02:00
Vfs_io_waiter_registry &_vfs_io_waiter_registry;
Dataspace_registry &_registry;
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
public:
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
noux: API transition This patch removes the dependency of the deprecated Genode API, fixes the coding style, and removes the "random" file system (superseded by the VFS plugin mechanism). Ref #1987
2017-01-06 12:12:39 +01:00
Local_rom_factory(Allocator &alloc, Env &env, Rpc_entrypoint &ep,
VFS: construct file-systems using Vfs::Env object Reduce the size and forward compatibility of VFS file-system constructors by passing an object holding accessors for 'Genode::Env', 'Genode::Allocator', response handlers, and the root file-system. Fix #2742
2018-04-03 15:59:35 +02:00
Vfs::File_system &root_dir,
VFS: nonblocking interface The VFS library can be used in single-threaded or multi-threaded environments and depending on that, signals are handled by the same thread which uses the VFS library or possibly by a different thread. If a VFS plugin needs to block to wait for a signal, there is currently no way which works reliably in both environments. For this reason, this commit makes the interface of the VFS library nonblocking, similar to the File_system session interface. The most important changes are: - Directories are created and opened with the 'opendir()' function and the directory entries are read with the recently introduced 'queue_read()' and 'complete_read()' functions. - Symbolic links are created and opened with the 'openlink()' function and the link target is read with the 'queue_read()' and 'complete_read()' functions and written with the 'write()' function. - The 'write()' function does not wait for signals anymore. This can have the effect that data written by a VFS library user has not been processed by a file system server yet when the library user asks for the size of the file or closes it (both done with RPC functions at the file system server). For this reason, a user of the VFS library should request synchronization before calling 'stat()' or 'close()'. To make sure that a file system server has processed all write request packets which a client submitted before the synchronization request, synchronization is now requested at the file system server with a synchronization packet instead of an RPC function. Because of this change, the synchronization interface of the VFS library is now split into 'queue_sync()' and 'complete_sync()' functions. Fixes #2399
2017-08-15 20:51:53 +02:00
Vfs_io_waiter_registry &vfs_io_waiter_registry,
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
Dataspace_registry &registry)
:
VFS: nonblocking interface The VFS library can be used in single-threaded or multi-threaded environments and depending on that, signals are handled by the same thread which uses the VFS library or possibly by a different thread. If a VFS plugin needs to block to wait for a signal, there is currently no way which works reliably in both environments. For this reason, this commit makes the interface of the VFS library nonblocking, similar to the File_system session interface. The most important changes are: - Directories are created and opened with the 'opendir()' function and the directory entries are read with the recently introduced 'queue_read()' and 'complete_read()' functions. - Symbolic links are created and opened with the 'openlink()' function and the link target is read with the 'queue_read()' and 'complete_read()' functions and written with the 'write()' function. - The 'write()' function does not wait for signals anymore. This can have the effect that data written by a VFS library user has not been processed by a file system server yet when the library user asks for the size of the file or closes it (both done with RPC functions at the file system server). For this reason, a user of the VFS library should request synchronization before calling 'stat()' or 'close()'. To make sure that a file system server has processed all write request packets which a client submitted before the synchronization request, synchronization is now requested at the file system server with a synchronization packet instead of an RPC function. Because of this change, the synchronization interface of the VFS library is now split into 'queue_sync()' and 'complete_sync()' functions. Fixes #2399
2017-08-15 20:51:53 +02:00
_alloc(alloc), _env(env), _ep(ep), _root_dir(root_dir),
_vfs_io_waiter_registry(vfs_io_waiter_registry),
_registry(registry)
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
{ }
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
Rom_session_component &create(Args const &args, Affinity) override
{
try {
Rom_session_component::Name const rom_name =
label_from_args(args.string()).last_element();
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
noux: API transition This patch removes the dependency of the deprecated Genode API, fixes the coding style, and removes the "random" file system (superseded by the VFS plugin mechanism). Ref #1987
2017-01-06 12:12:39 +01:00
return *new (_alloc)
VFS: nonblocking interface The VFS library can be used in single-threaded or multi-threaded environments and depending on that, signals are handled by the same thread which uses the VFS library or possibly by a different thread. If a VFS plugin needs to block to wait for a signal, there is currently no way which works reliably in both environments. For this reason, this commit makes the interface of the VFS library nonblocking, similar to the File_system session interface. The most important changes are: - Directories are created and opened with the 'opendir()' function and the directory entries are read with the recently introduced 'queue_read()' and 'complete_read()' functions. - Symbolic links are created and opened with the 'openlink()' function and the link target is read with the 'queue_read()' and 'complete_read()' functions and written with the 'write()' function. - The 'write()' function does not wait for signals anymore. This can have the effect that data written by a VFS library user has not been processed by a file system server yet when the library user asks for the size of the file or closes it (both done with RPC functions at the file system server). For this reason, a user of the VFS library should request synchronization before calling 'stat()' or 'close()'. To make sure that a file system server has processed all write request packets which a client submitted before the synchronization request, synchronization is now requested at the file system server with a synchronization packet instead of an RPC function. Because of this change, the synchronization interface of the VFS library is now split into 'queue_sync()' and 'complete_sync()' functions. Fixes #2399
2017-08-15 20:51:53 +02:00
Rom_session_component(_alloc, _env, _ep, _root_dir,
_vfs_io_waiter_registry, _registry,
rom_name);
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
}
Streamline exception types This patch reduces the number of exception types by facilitating globally defined exceptions for common usage patterns shared by most services. In particular, RPC functions that demand a session-resource upgrade not longer reflect this condition via a session-specific exception but via the 'Out_of_ram' or 'Out_of_caps' types. Furthermore, the 'Parent::Service_denied', 'Parent::Unavailable', 'Root::Invalid_args', 'Root::Unavailable', 'Service::Invalid_args', 'Service::Unavailable', and 'Local_service::Factory::Denied' types have been replaced by the single 'Service_denied' exception type defined in 'session/session.h'. This consolidation eases the error handling (there are fewer exceptions to handle), alleviates the need to convert exceptions along the session-creation call chain, and avoids possible aliasing problems (catching the wrong type with the same name but living in a different scope).
2017-05-07 22:03:22 +02:00
catch (Rom_connection::Rom_connection_failed) {
throw Service_denied(); }
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
}
void upgrade(Rom_session_component &, Args const &) override { }
void destroy(Rom_session_component &session) override
{
noux: API transition This patch removes the dependency of the deprecated Genode API, fixes the coding style, and removes the "random" file system (superseded by the VFS plugin mechanism). Ref #1987
2017-01-06 12:12:39 +01:00
Genode::destroy(_alloc, &session);
Adapt high-level components to new parent API This patch adjusts the various users of the 'Child' API to the changes on the account of the new non-blocking parent interface. It also removes the use of the no-longer-available 'Connection::KEEP_OPEN' feature. With the adjustment, we took the opportunity to redesign several components to fit the non-blocking execution model much better, in particular the demo applications. Issue #2120
2016-11-23 17:07:49 +01:00
}
};
noux: Keep track of how dataspaces are used This patch eliminates the "no attachment at..." warnings, which were caused by a use-after-free problem of dataspaces. When a dataspace was destroyed, the users of the dataspace were not informed and therefore could not revert possible attachments to RM sessions. The fix introduces a callback mechanism that allows dataspace users (i.e., RM regions) to register for the event that a dataspace vanishes. The following types of dataspaces are handled: * RAM dataspaces * ROM dataspaces * The process binary * The binary of the dynamic linker * Args dataspace * Sysio dataspace * Env dataspace * managed RM dataspaces The handling of ROM dataspaces is still not complete. When forking, the ROM dataspace of the parent process gets just reused without creating proper meta data ('Dataspace_info') for the forked process. Similar issues might arise from other special dataspaces (e.g., args, env, sysio). This patch removes all "no attachment at..." warnings except for one (an attachment at 0). Issue #485
2013-07-18 16:27:42 +02:00
#endif /* _NOUX__LOCAL_ROM_SERVICE_H_ */
Reference in New Issue Copy Permalink