Re: [PATCH] nolibc: Don't use `malloc()` and `free()` as the function name

[Jens Axboe <axboe@xxxxxxxxx>]

On Sun, 23 Jan 2022 14:42:30 +0700, Ammar Faizi wrote:
> Miyasaki reports that liburing with CONFIG_NOLIBC breaks apps that
> use libc. The first spotted issue was a realloc() call that results
> in an invalid pointer, and then the program exits with SIGABRT.
> 
> The cause is liburing nolibc overrides malloc() and free() from the
> libc (especially when we statically link the "liburing.a" to the apps
> that use libc).
> 
> [...]

Applied, thanks!

[1/1] nolibc: Don't use `malloc()` and `free()` as the function name
      commit: 29ff69397fa13478b5619201347c51159874279e

Best regards,
-- 
Jens Axboe