diff options
Diffstat (limited to 'newlib/libc/stdlib/mlock.c')
| -rw-r--r-- | newlib/libc/stdlib/mlock.c | 26 |
1 files changed, 19 insertions, 7 deletions
diff --git a/newlib/libc/stdlib/mlock.c b/newlib/libc/stdlib/mlock.c index c603fbcda..378b4e691 100644 --- a/newlib/libc/stdlib/mlock.c +++ b/newlib/libc/stdlib/mlock.c @@ -21,13 +21,13 @@ TRAD_SYNOPSIS struct _reent *<[reent]>; DESCRIPTION -The <<malloc>> family of routines call these functions when they need -to lock the memory pool. The version of these routines supplied in -the library does not do anything. If multiple threads of execution -can call <<malloc>>, or if <<malloc>> can be called reentrantly, then -you need to define your own versions of these functions in order to -safely lock the memory pool during a call. If you do not, the memory -pool may become corrupted. +The <<malloc>> family of routines call these functions when they need to lock +the memory pool. The version of these routines supplied in the library use +the lock API defined in sys/lock.h. If multiple threads of execution can +call <<malloc>>, or if <<malloc>> can be called reentrantly, then you need to +define your own versions of these functions in order to safely lock the +memory pool during a call. If you do not, the memory pool may become +corrupted. A call to <<malloc>> may call <<__malloc_lock>> recursively; that is, the sequence of calls may go <<__malloc_lock>>, <<__malloc_lock>>, @@ -37,16 +37,28 @@ that it already holds. */ #include <malloc.h> +#include <sys/lock.h> + +#ifndef __SINGLE_THREAD__ +__LOCK_INIT_RECURSIVE(static, __malloc_lock_object); +#endif void __malloc_lock (ptr) struct _reent *ptr; { +#ifndef __SINGLE_THREAD__ + __lock_acquire_recursive (__malloc_lock_object); +#endif } void __malloc_unlock (ptr) struct _reent *ptr; { +#ifndef __SINGLE_THREAD__ + __lock_release_recursive (__malloc_lock_object); +#endif } + #endif |