Will no longer fail if the recursive_lock couldn't be created - that does
*not* change the previous behaviour (well, I added some debug output), since the former recursive_lock_create() did always return B_OK, no matter if the lock could be initialized or not. git-svn-id: file:///srv/svn/repos/haiku/trunk/current@3680 a95241bf-73f2-0310-859d-f6bbb57e9c96
This commit is contained in:
@@ -620,8 +620,11 @@ vm_translation_map_create(vm_translation_map *new_map, bool kernel)
|
||||
// initialize the new object
|
||||
new_map->ops = &tmap_ops;
|
||||
new_map->map_count = 0;
|
||||
if (recursive_lock_create(&new_map->lock) < 0)
|
||||
return ENOMEM;
|
||||
|
||||
// ToDo: lock creation fails at this point during the boot process!
|
||||
// (it will boot anyway, for now, the return code was wrong previously...)
|
||||
if (recursive_lock_init(&new_map->lock, "vm tm rlock") < 0)
|
||||
dprintf("vm_translation_map_create(): creating lock failed - continuing...");
|
||||
|
||||
new_map->arch_data = (vm_translation_map_arch_info *)malloc(sizeof(vm_translation_map_arch_info));
|
||||
if (new_map == NULL) {
|
||||
|
||||
Reference in New Issue
Block a user