How useful should copy_file_range() be?

Posted Feb 20, 2021 17:01 UTC (Sat) by markh (subscriber, #33984)
In reply to: How useful should copy_file_range() be? by jengelh
Parent article: How useful should copy_file_range() be?

The bug is that the kernel is reporting it as a regular file (in st_mode), but then does not satisfy the requirements for regular files. If the kernel does not want to satisfy those requirements, all that is needed is to report it as a type of file that does not have the requirements that it cannot satisfy. It is not reasonable to expect userspace programs to somehow guess that a file reported as a regular file cannot be relied upon to behave as such.

How useful should copy_file_range() be?

Posted Feb 23, 2021 19:02 UTC (Tue) by jsmith45 (guest, #125263) [Link] (1 responses)

Very true. The problem is that there is almost certainly a bunch of programs out there that will break if the file types of /proc pseudofiles changes to be anything but a normal file.

How useful should copy_file_range() be?

Posted Feb 25, 2021 11:12 UTC (Thu) by zuzzurro (subscriber, #61118) [Link]

Given the amount of confusion that is visible in the thread where kernel programmers are trying to find the best way to fix this I find it sad that people have tried to just throw the issue off to the userland.