all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: David Koppelman <koppel@ece.lsu.edu>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Dataloss copying file using copy-file on RHEL 8.
Date: Sun, 16 Feb 2020 10:25:33 -0600	[thread overview]
Message-ID: <yg5r1yusdmq.fsf@cyc.ece.lsu.edu> (raw)
In-Reply-To: <a5d18981-5546-5582-6a04-fe8c2cfb20bb@cs.ucla.edu> (Paul Eggert's message of "Fri, 14 Feb 2020 07:58:39 -0800")

Red Hat has verified the copy_file_range flaw, so it's not a quirk
unique to my system. They reproduced the flaw, using Paul Eggert's
reproducer with futimens added, on kernel 4.18.0-80.11.2.el8_0.x86_64
and I'm suffering it on 4.18.0-147.3.1.el8_1.x86_64. The copy ran
correctly on 5.6.0-0.rc0.git5.1.fc32.x86_64.

I've asked twice that the bug,
https://bugzilla.redhat.com/show_bug.cgi?id=1803162, be made publicly
accessible.

Paul Eggert <eggert@cs.ucla.edu> writes:

> On 2/14/20 7:22 AM, David Koppelman wrote:
>> I've reported the problem in Red Hat bug 1803162.
>> https://bugzilla.redhat.com/show_bug.cgi?id=1803162
>
> Thanks, but I am not authorized to access that Bug#. I suppose I could
> also file a public (Fedora) bug report but I wouldn't like to bother
> them if they fix the bug quickly anyway.



  parent reply	other threads:[~2020-02-16 16:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-12 22:37 Dataloss copying file using copy-file on RHEL 8 David Koppelman
2020-02-13  1:32 ` Paul Eggert
2020-02-13 17:08   ` David Koppelman
2020-02-13 18:57     ` Paul Eggert
2020-02-14 15:22       ` David Koppelman
2020-02-14 15:58         ` Paul Eggert
2020-02-14 16:03           ` Dmitry Gutov
2020-02-16 16:25           ` David Koppelman [this message]
2020-02-18 16:10           ` David Koppelman

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=yg5r1yusdmq.fsf@cyc.ece.lsu.edu \
    --to=koppel@ece.lsu.edu \
    --cc=eggert@cs.ucla.edu \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.