Re: should a copy_file_range(2) syscall be interrupted via a signal

From: Hans Petter Selasky <hps_at_selasky.org>
Date: Fri, 5 Jul 2019 15:58:45 +0200

On 2019-07-05 02:28, Rick Macklem wrote:
> I am thinking that copy_file_range(2) should do this also.
> However, if it returns an error, it is impossible for the caller to know how much
> of the data range got copied.

How can you kill a program stuck on copy_file_range(2) w/o catching signals?

--HPS

Received on Fri Jul 05 2019 - 11:59:28 UTC

This message: [ Message body ]
Next message: Alan Somers: "Re: test program for copy_file_range(2)"
Previous message: Rick Macklem: "test program for copy_file_range(2)"
In reply to: Rick Macklem: "should a copy_file_range(2) syscall be interrupted via a signal"
Next in thread: Rick Macklem: "Re: should a copy_file_range(2) syscall be interrupted via a signal"
Reply: Rick Macklem: "Re: should a copy_file_range(2) syscall be interrupted via a signal"

Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ]

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:41:21 UTC