From db8890ba1d0016e7f623fbd309d2395b602d067c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Axel=20D=C3=B6rfler?= Date: Fri, 25 May 2007 14:38:59 +0000 Subject: [PATCH] * The mutex was obviously never initialized, and therefore mutex_unlock() panicked here when trying to build Haiku. * Also probably fixed a memory hole, at least how BFS is using delete_driver_settings(); it might be a general problem of the implementation with regards to parse_driver_settings_string(), though. git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@21240 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/tools/fs_shell/driver_settings.cpp | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/tools/fs_shell/driver_settings.cpp b/src/tools/fs_shell/driver_settings.cpp index eda388893c..1418d5240a 100644 --- a/src/tools/fs_shell/driver_settings.cpp +++ b/src/tools/fs_shell/driver_settings.cpp @@ -617,15 +617,15 @@ fssh_unload_driver_settings(void *handle) if (!check_handle(handle)) return FSSH_B_BAD_VALUE; +#if 0 mutex_lock(&sLock); // ToDo: as soon as "/boot" is accessible, we should start throwing away settings -#if 0 if (--handle->ref_count == 0) { list_remove_link(&handle->link); } else -#endif handle = NULL; mutex_unlock(&sLock); +#endif if (handle != NULL) free_settings((settings_handle*)handle);