Date: Fri, 5 Jul 2019 15:58:45 +0200 From: Hans Petter Selasky <hps@selasky.org> To: Rick Macklem <rmacklem@uoguelph.ca>, "freebsd-current@FreeBSD.org" <freebsd-current@FreeBSD.org> Cc: "kib@freebsd.org" <kib@FreeBSD.org>, Alan Somers <asomers@freebsd.org> Subject: Re: should a copy_file_range(2) syscall be interrupted via a signal Message-ID: <8c7707d7-f315-d613-705f-40b1619a7553@selasky.org> In-Reply-To: <YTXPR01MB0285E79DFAAE250FD7A7A181DDF50@YTXPR01MB0285.CANPRD01.PROD.OUTLOOK.COM> References: <YTXPR01MB0285E79DFAAE250FD7A7A181DDF50@YTXPR01MB0285.CANPRD01.PROD.OUTLOOK.COM>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8c7707d7-f315-d613-705f-40b1619a7553>