Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20140310095054.31d6769e@mt.lv>
Date: Mon, 10 Mar 2014 09:50:54 +0000
From: juris <juris@...lv>
To: musl@...ts.openwall.com
Subject: Re: Release schedule & tasks for 1.0

On Mon, 10 Mar 2014 03:04:11 -0400
Rich Felker <dalias@...ifal.cx> wrote:

> If anyone has outstanding bugs that can be fixed quickly and
> non-invasively (low risk from making changes) please [re-]report them
> in this thread.

Not exactly a bug fix, but does something like this qualify for 1.0 inclusion?
Lifted it from http://article.gmane.org/gmane.linux.lib.musl.general/1255/ and prettied up a little.


diff --git a/include/stdlib.h b/include/stdlib.h
index f034c6e..7c07c50 100644
--- a/include/stdlib.h
+++ b/include/stdlib.h
@@ -40,6 +40,7 @@ void *calloc (size_t, size_t);
 void *realloc (void *, size_t);
 void free (void *);
 void *aligned_alloc(size_t alignment, size_t size);
+size_t malloc_usable_size (void *);
 
 _Noreturn void abort (void);
 int atexit (void (*) (void));
diff --git a/src/malloc/malloc.c b/src/malloc/malloc.c
index d6ad904..771e6be 100644
--- a/src/malloc/malloc.c
+++ b/src/malloc/malloc.c
@@ -533,3 +533,8 @@ void free(void *p)
 
        unlock_bin(i);
 }
+
+size_t malloc_usable_size(void *p)
+{
+       return CHUNK_SIZE(MEM_TO_CHUNK(p)) - OVERHEAD;
+}


Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.