Because Debian coreutils 9.1-1 "cp" silently falls back to copy_file_range()
after FICLONE reports EIO, "cp" can transfer incorrect bytes. Linux syscalls
having a file descriptor parameter report EIO after a fault in the underlying
device. The affected file is not recoverable in the general case,
On 02/01/2023 06:36, Noah Misch wrote:
Because Debian coreutils 9.1-1 "cp" silently falls back to copy_file_range()
after FICLONE reports EIO, "cp" can transfer incorrect bytes. Linux syscalls
having a file descriptor parameter report EIO after a fault in the underlying
device. The affected fil
On Jan 02 2023, Pádraig Brady wrote:
> + /* Note error set is consistent with copy_file_range(). */
> + bool no_clone_attempted = errno == ENOSYS || is_ENOTSUP (errno)
> +|| errno == EINVAL || errno == EBADF
> +
On 02/01/2023 13:28, Andreas Schwab wrote:
On Jan 02 2023, Pádraig Brady wrote:
+ /* Note error set is consistent with copy_file_range(). */
+ bool no_clone_attempted = errno == ENOSYS || is_ENOTSUP (errno)
+|| errno == EINVAL || errno == E
On 2022-10-14 09:24, chandler wrote:
Please no excuses about how this will break other programs
Unfortunately backward-compatibility concerns are real, which means
we're not likely to make a big change to -h's behavior at this point.
You can use --si instead.
Assuming you're talking about '
On 2023-01-02 13:22, Chandler Sobel-Sorenson wrote:
Unfortunately backward-compatibility concerns are real,
Such as?
I imagine lots of programs read the current output format. GNU 'sort'
does. I haven't investigated all such programs.
The current behavior has been in place since Larry Mc
On 20/11/2022 03:50, Paul Eggert wrote:
Although we inadvertently removed support for weird devices in 2009 by
commit 55efc5f3ee485b3e31a91c331f07c89aeccc4e89, and nobody seems to
care (because people use dd or whatever to deal with weird devices), I
think it'd be better to limit the fix to regul
On 2023-01-02 15:03, Pádraig Brady wrote:
On 20/11/2022 03:50, Paul Eggert wrote:
Although we inadvertently removed support for weird devices in 2009 by
commit 55efc5f3ee485b3e31a91c331f07c89aeccc4e89, and nobody seems to
care (because people use dd or whatever to deal with weird devices), I
thi
On 02/01/2023 23:18, Paul Eggert wrote:
On 2023-01-02 15:03, Pádraig Brady wrote:
On 20/11/2022 03:50, Paul Eggert wrote:
Although we inadvertently removed support for weird devices in 2009 by
commit 55efc5f3ee485b3e31a91c331f07c89aeccc4e89, and nobody seems to
care (because people use dd or wh
Paul Eggert wrote on 1/2/23 1:28 PM:
Unfortunately backward-compatibility concerns are real,
Such as?
which means we're not likely to make a big change to -h's behavior at this
point. You can use --si instead.
While --si produces correct output, this does not address the subject of this b
10 matches
Mail list logo
