From: Jens Axboe <axboe@kernel.dk>
To: io-uring@vger.kernel.org,
"Martin K. Petersen" <martin.petersen@oracle.com>
Subject: Re: [PATCH] man: Fix syscall wrappers in example code
Date: Wed, 16 Apr 2025 14:11:08 -0600 [thread overview]
Message-ID: <174483426882.431568.3152351618925531263.b4-ty@kernel.dk> (raw)
In-Reply-To: <yq1o6wveuun.fsf@ca-mkp.ca.oracle.com>
On Wed, 16 Apr 2025 16:08:53 -0400, Martin K. Petersen wrote:
> The example code in io_uring.7 provides two wrappers for the io_uring
> syscalls. However, the example fails to take into account that glibc's
> syscall(2) returns -1 and sets errno on failure. This means that any
> errors returned by the provided wrapper functions will be reported as
> -EPERM which could lead to incorrect error handling actions being
> taken.
>
> [...]
Applied, thanks!
[1/1] man: Fix syscall wrappers in example code
commit: 4c9be7fdbb83b9e2872721fb026befa052f65ded
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2025-04-16 20:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-16 20:08 [PATCH] man: Fix syscall wrappers in example code Martin K. Petersen
2025-04-16 20:11 ` 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=174483426882.431568.3152351618925531263.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=io-uring@vger.kernel.org \
--cc=martin.petersen@oracle.com \
/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