From: Jonathan Wakely <jwakely@redhat.com>
To: "Jannik Glückert" <jannik.glueckert@gmail.com>
Cc: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH v2 1/2] libstdc++: use copy_file_range, improve sendfile in filesystem::copy_file
Date: Mon, 20 Mar 2023 15:18:16 +0000 [thread overview]
Message-ID: <CACb0b4nkp3Kz3SxZs=-kYRv0ekZWUvTipt2Juy8Tyr++ZObnLw@mail.gmail.com> (raw)
In-Reply-To: <CACb0b4=qA7ibsvsBZR7ry+M5Lks-zuB=h+5eebEfPHaeRC3taw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
On Mon, 20 Mar 2023 at 15:16, Jonathan Wakely wrote:
>
>
> On Wed, 15 Mar 2023 at 19:30, Jannik Glückert via Libstdc++ <
> libstdc++@gcc.gnu.org> wrote:
>
>> This iteration improves error handling for copy_file_range,
>> particularly around undocumented error codes in earlier kernel
>> versions.
>> Additionally this fixes the userspace copy fallback to handle
>> zero-length files such as in
>> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108178.
>>
>> Lastly, the case "src gets resized during the copy loop" is now
>> considered and will return true once the loop hits EOF (this is the
>> only situation, aside from a zero-length src, where sendfile and
>> copy_file_range return 0).
>>
>
> I've applied this patch (with some whitespace fixes) and started testing
> it. I'm seeing some regressions:
>
> FAIL: experimental/filesystem/operations/copy.cc execution test
> FAIL: experimental/filesystem/operations/copy_file.cc execution test
>
> The failures in the log look like:
>
> terminate called after throwing an instance of
> 'std::experimental::filesystem::v1::__cxx11::filesystem_error'
> what(): filesystem error: cannot copy: Input/output error
> [filesystem-test.copy.2900321341.ySWT77]
> [filesystem-test.copy.2900321342.vjeAar]
> FAIL: experimental/filesystem/operations/copy.cc execution test
>
Not just the Filesystem TS versions of those tests, but the std::filesystem
ones too:
FAIL: 27_io/filesystem/operations/copy.cc execution test
FAIL: 27_io/filesystem/operations/copy_file.cc execution test
next prev parent reply other threads:[~2023-03-20 15:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-15 19:29 Jannik Glückert
2023-03-20 15:16 ` Jonathan Wakely
2023-03-20 15:18 ` Jonathan Wakely [this message]
2023-03-20 22:27 ` [PATCH v2 1/2] libstdc++: also use sendfile for big files Jonathan Wakely
2023-03-20 22:30 ` Jonathan Wakely
2023-03-22 12:14 ` Jonathan Wakely
2023-03-22 12:18 ` Jonathan Wakely
2023-03-22 12:20 ` Jonathan Wakely
2023-06-06 11:37 ` Jonathan Wakely
2023-06-06 11:36 ` Jonathan Wakely
2023-06-06 11:35 ` Jonathan Wakely
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='CACb0b4nkp3Kz3SxZs=-kYRv0ekZWUvTipt2Juy8Tyr++ZObnLw@mail.gmail.com' \
--to=jwakely@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jannik.glueckert@gmail.com \
--cc=libstdc++@gcc.gnu.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).