summaryrefslogtreecommitdiffstats
path: root/cpukit/libcsupport/src/alignedalloc.c
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2021-05-05 08:49:52 +0200
committerSebastian Huber <sebastian.huber@embedded-brains.de>2021-05-06 08:03:58 +0200
commit2c5199bb049efe8e29cd12461dc57bd6e30388e8 (patch)
tree31086387522ae9803a5a15bb33ee014ed96eeaf8 /cpukit/libcsupport/src/alignedalloc.c
parentlibc: Reimplement posix_memlign() (diff)
downloadrtems-2c5199bb049efe8e29cd12461dc57bd6e30388e8.tar.bz2
Return NULL for zero size allocations
In POSIX, zero size memory allocations are implementation-defined behaviour. The implementation has two options: https://pubs.opengroup.org/onlinepubs/9699919799/functions/malloc.html https://pubs.opengroup.org/onlinepubs/9699919799/functions/posix_memalign.html Linux and FreeBSD return a unique pointer for zero size memory allocations. Return NULL on RTEMS to more likely catch the use of a zero size memory area by erroneous applications. Update #4390.
Diffstat (limited to 'cpukit/libcsupport/src/alignedalloc.c')
-rw-r--r--cpukit/libcsupport/src/alignedalloc.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/cpukit/libcsupport/src/alignedalloc.c b/cpukit/libcsupport/src/alignedalloc.c
index b552fc2a0f..9c9ea83bd8 100644
--- a/cpukit/libcsupport/src/alignedalloc.c
+++ b/cpukit/libcsupport/src/alignedalloc.c
@@ -35,6 +35,10 @@
void *aligned_alloc( size_t alignment, size_t size )
{
+ if ( size == 0 ) {
+ return NULL;
+ }
+
return rtems_heap_allocate_aligned_with_boundary( size, alignment, 0 );
}