From: Jens Axboe <[email protected]>
To: Pavel Begunkov <[email protected]>,
Alexander Viro <[email protected]>,
[email protected], [email protected],
[email protected]
Subject: Re: [RFC] splice/tee: len=0 fast path after validity check
Date: Sat, 9 May 2020 08:42:56 -0600 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <14d4955e8c232ea7d2cbb2c2409be789499e0452.1589013737.git.asml.silence@gmail.com>
On 5/9/20 2:46 AM, Pavel Begunkov wrote:
> When len=0, splice() and tee() return 0 even if specified fds are
> invalid, hiding errors from users. Move len=0 optimisation later after
> basic validity checks.
>
> before:
> splice(len=0, fd_in=-1, ...) == 0;
>
> after:
> splice(len=0, fd_in=-1, ...) == -EBADF;
I'm not sure what the purpose of this would be. It probably should have
been done that way from the beginning, but it wasn't. While there's
very little risk of breaking any applications due to this change, it
also seems like a pointless exercise at this point.
So my suggestion would be to just leave it alone.
--
Jens Axboe
next prev parent reply other threads:[~2020-05-09 14:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-09 8:46 [RFC] splice/tee: len=0 fast path after validity check Pavel Begunkov
2020-05-09 14:42 ` Jens Axboe [this message]
2020-05-09 16:03 ` Pavel Begunkov
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] \
/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