NetBSD/sys/dev/dmover
dsl 2a54322c7b If a multithreaded app closes an fd while another thread is blocked in
read/write/accept, then the expectation is that the blocked thread will
exit and the close complete.
Since only one fd is affected, but many fd can refer to the same file,
the close code can only request the fs code unblock with ERESTART.
Fixed for pipes and sockets, ERESTART will only be generated after such
a close - so there should be no change for other programs.
Also rename fo_abort() to fo_restart() (this used to be fo_drain()).
Fixes PR/26567
2009-12-20 09:36:05 +00:00
..
Makefile
dmover_backend.c Add #include <sys/simplelock.h> 2008-01-05 02:47:03 +00:00
dmover_io.c If a multithreaded app closes an fd while another thread is blocked in 2009-12-20 09:36:05 +00:00
dmover_io.h
dmover_process.c Add #include <sys/simplelock.h> 2008-01-05 02:47:03 +00:00
dmover_request.c Start detangling lock.h from intr.h. This is likely to cause short term 2008-01-04 21:17:40 +00:00
dmover_session.c Start detangling lock.h from intr.h. This is likely to cause short term 2008-01-04 21:17:40 +00:00
dmover_util.c
dmovervar.h
files.dmover
swdmover.c Start detangling lock.h from intr.h. This is likely to cause short term 2008-01-04 21:17:40 +00:00