From: Jens Axboe <[email protected]>
To: Ammar Faizi <[email protected]>
Cc: Alviro Iskandar Setiawan <[email protected]>,
Tea Inside Mailing List <[email protected]>,
io-uring Mailing List <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Miyasaki Kohaku <[email protected]>
Subject: Re: [PATCH] nolibc: Don't use `malloc()` and `free()` as the function name
Date: Sun, 23 Jan 2022 09:36:26 -0700 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
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
prev parent reply other threads:[~2022-01-23 16:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-23 7:42 [PATCH] nolibc: Don't use `malloc()` and `free()` as the function name Ammar Faizi
2022-01-23 16:36 ` Jens Axboe [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=164295578635.5600.9693251485824219620.b4-ty@kernel.dk \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox