Date: Wed, 10 Apr 2024 14:11:46 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 271675] cp: Interrupted system call Message-ID: <bug-271675-227-sjKxUGnlvJ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-271675-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | previous in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=271675 --- Comment #8 from Ivan Rozhuk <rozhuk.im@gmail.com> --- (In reply to Mark Johnston from comment #7) According to man copy_file_range [1] EINTR also may happen "for files on some NFS mounts.", so it is not new problem, it is documented behavior. You may ask authors, see here: https://reviews.freebsd.org/D20584 Since it is documented, it should be handled, like it handled for send()/recv()/write()/read()/connect()/kevent()/epoll_wait()/nanosleep()... in multiple well designed apps. Documented error handling is not workaround. You may continue research and probably as result you will find out that it work as it should. 11 month is gone, I do not want back to this investigation. Probably also patch required for: bin/cat/cat.c usr.bin/xinstall/xinstall.c and multiple staff in tests. 1: https://man.freebsd.org/cgi/man.cgi?query=copy_file_range&apropos=0&sektion=2&manpath=FreeBSD+14.0-STABLE&arch=default&format=html -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-271675-227-sjKxUGnlvJ>