public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/106296] New: Consider using fsync or fdatasync in filesystem::copy_file
@ 2022-07-14 13:32 redi at gcc dot gnu.org
  2022-07-14 13:34 ` [Bug libstdc++/106296] " redi at gcc dot gnu.org
  0 siblings, 1 reply; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2022-07-14 13:32 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106296

            Bug ID: 106296
           Summary: Consider using fsync or fdatasync in
                    filesystem::copy_file
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: redi at gcc dot gnu.org
  Target Milestone: ---

Writing the file to disk might be slow and could be interrupted by a signal. If
we don't flush explicitly, it will happen when closing the file descriptor, but
if that's interrupted by a signal we don't know if the file was closed or not.

Consider using fsync to flush the data explicitly, looping on EINTR, so that
there's nothing more to do when closing the file.

^ permalink raw reply	[flat|nested] 2+ messages in thread
* [Bug libstdc++/106296] Consider using fsync or fdatasync in filesystem::copy_file
  2022-07-14 13:32 [Bug libstdc++/106296] New: Consider using fsync or fdatasync in filesystem::copy_file redi at gcc dot gnu.org
@ 2022-07-14 13:34 ` redi at gcc dot gnu.org
  0 siblings, 0 replies; 2+ messages in thread
From: redi at gcc dot gnu.org @ 2022-07-14 13:34 UTC (permalink / raw)
  To: gcc-bugs

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106296

--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> ---
However, see https://github.com/boostorg/filesystem/issues/186

^ permalink raw reply	[flat|nested] 2+ messages in thread
end of thread, other threads:[~2022-07-14 13:34 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-07-14 13:32 [Bug libstdc++/106296] New: Consider using fsync or fdatasync in filesystem::copy_file redi at gcc dot gnu.org
2022-07-14 13:34 ` [Bug libstdc++/106296] " redi at gcc dot gnu.org

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).