From: Ammar Faizi <[email protected]>
To: Jens Axboe <[email protected]>
Cc: Ammar Faizi <[email protected]>,
Pavel Begunkov <[email protected]>,
Gilang Fachrezy <[email protected]>,
io-uring Mailing List <[email protected]>,
VNLX Kernel Department <[email protected]>,
GNU/Weeb Mailing List <[email protected]>,
Dylan Yudaken <[email protected]>,
Stefano Garzarella <[email protected]>
Subject: [PATCH liburing v1] liburing.map: Export `io_uring_{enable_rings,register_restrictions}`
Date: Sat, 14 Jan 2023 10:54:05 +0700 [thread overview]
Message-ID: <[email protected]> (raw)
From: Ammar Faizi <[email protected]>
When adding these two functions, Stefano didn't add
io_uring_enable_rings() and io_uring_register_restrictions() to
liburing.map. It causes a linking problem. Add them to liburing.map.
This issue hits liburing 2.0 to 2.3.
Closes: https://github.com/axboe/liburing/pull/774
Fixes: https://github.com/axboe/liburing/issues/773
Fixes: https://github.com/facebook/folly/issues/1908
Fixes: d2654b1ac886 ("Add helper to enable rings")
Fixes: 25cf9b968a27 ("Add helper to register restrictions")
Cc: Dylan Yudaken <[email protected]>
Cc: Stefano Garzarella <[email protected]>
Signed-off-by: Ammar Faizi <[email protected]>
---
src/liburing.map | 3 +++
1 file changed, 3 insertions(+)
diff --git a/src/liburing.map b/src/liburing.map
index 67aebae..1dbe765 100644
--- a/src/liburing.map
+++ b/src/liburing.map
@@ -73,4 +73,7 @@ LIBURING_2.4 {
io_uring_major_version;
io_uring_minor_version;
io_uring_check_version;
+
+ io_uring_enable_rings;
+ io_uring_register_restrictions;
} LIBURING_2.3;
base-commit: 0df8a379e929641699c2ab1f42de1efd2515b908
--
Ammar Faizi
next reply other threads:[~2023-01-14 3:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-14 3:54 Ammar Faizi [this message]
2023-01-14 3:57 ` [PATCH liburing v1] liburing.map: Export `io_uring_{enable_rings,register_restrictions}` Jens Axboe
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 \
[email protected] \
[email protected] \
[email protected] \
[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